-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Telephone crashes with "Use DNS SRV" #669
Comments
Hi @eofster, 🔴 I think I have been able to reliably reproduce the crash within the
|
Afaik stun.freeswitch.org has no SRV records set. So while Telephone should probably not crash over that you should not enable 'Use DNS SRV' for a domain that doesn't support it. |
Hi @olku,
Thanks. Yes, I also thought so. The app crashes similarly with other STUN servers like
Yes again -- this is the main problem. It would be okay if the SIP connection or calls failed, but the unexpected crash is the main issue. Also, it's not obvious how to recover from the crash, i.e. once you've ticked the "Use DNS SRV" option by mistake, you can't easily disable it. The app will crash every time you restart before you get a chance to disable this option. See my comments here to recover from "wrong data" (issue #668). Thank you. |
Are you building on Intel? Since I moved to Apple Silicon, I updated the building instructions for building a universal binary on Apple Silicon and kind of don't support building on Intel any more, only running on Intel. What might work is to use the older building instructions from the Readme. The version before it's been updated for making a universal binary from an ARM Mac. |
To recover from the crash, you can change the app settings via the macOS
|
Hi @eofster,
Yes, I'm building on Intel.
To confirm, I have added necessary patches to build d13b7d1 on Intel. All functionalities work as expected, except the "Use DNS SRV" crash mentioned above. Is this something (the crash) you are able to reproduce with your universal binary build? I don't have access to an "Apple Silicon" machine to test it. Thanks. |
That's the thing: I can't reproduce it with universal library on Apple Silicon. Closer to the release, I will also test how the universal library built on Apple Silicon works on Intel. But I won't be going back and testing the builds made on Intel. |
Hi @eofster,
📌 I'm trying to build the latest d13b7d1 commit for
x64_64
but am running into the following memory access violation insidememmove()
(originating fromPJSIP/PJSUA
):📌 The stack trace for the given thread (Treat 12 in this case) looks like the following:
📌 Following is my build system configuration:
📌 I have made the necessary adjustments to the
Telephone.xcodeproj
, compiledOpus
,LibreSSL
andPJSIP
libraries forx86_64
, and everything builds without issues, but when I run the freshly builtTelephone.app
, it runs into the access violation error mentioned above.📌 I have also tried building with the latest
Xcode_13.3_beta_3
, but still got the same error. Thanks.🟡 Would you be able to share some hints on what might be going on and how to prevent the crash? Thanks a lot!
The text was updated successfully, but these errors were encountered: