Skip to content
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

Voice SDK crash #638

Closed
larganaraztam opened this issue Nov 26, 2024 · 5 comments
Closed

Voice SDK crash #638

larganaraztam opened this issue Nov 26, 2024 · 5 comments

Comments

@larganaraztam
Copy link

larganaraztam commented Nov 26, 2024

Description

After five consecutive short calls, the next call throws an error consistently when it tries to connect (after Voice.connect)

FORTIFY: FD_SET: file descriptor 1114 >= FD_SETSIZE 1024

I tried to fix it by calling .release() after call is disconnected but it is not working.
Is it a SDK bug?

Thanks in advance

SDK log:
log

@afalls-twilio
Copy link
Contributor

afalls-twilio commented Dec 2, 2024

@larganaraztam This due to your device running out of file descriptors. This happens when your calls are not properly shutdown/ended before starting new ones.

@larganaraztam
Copy link
Author

larganaraztam commented Dec 2, 2024

@afalls-twilio Thank you. We are ending the calls by calling activeCall?.disconnect().
Then on the onDisconnected callback we call:
activeCall?.release()
activeCall = null

It seems to be ended well, but it fails after 5 or 6 calls. Are we missing somenthing to do it working well? Do you need other information?

By other hand, if we remove any other endpoints calls in our app but keeping only our access token endpoint call and the SDK connection, it works well for more than 10 calls then it fails with the same file descriptor issue. The use case is to call an IVR number, hangup after one or two seconds after call is connected, then call inmediatly to the same number.

The logcat error:
cap

@afalls-twilio
Copy link
Contributor

@larganaraztam are you waiting for the onDisconnected callback? also, are you able to reproduce it with the quickstart(This would provide us with a common codebase from which we can attempt to reproduce the issue)?

@larganaraztam
Copy link
Author

@afalls-twilio yes we wait until onDisconnected is called to make a new call, in the quickstart I can't reproduce, but in our app we are doing other network calls to get the token and other endpoints needed for the app after and before the call. Maybe it could be the issue about it?

@afalls-twilio
Copy link
Contributor

afalls-twilio commented Dec 11, 2024

@larganaraztam yeah, it possible. Also, are all the sdk method calls being made from the same thread? without being able to reproduce it with the quickstart we can't easily create a fix, unfortunately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants