-
Notifications
You must be signed in to change notification settings - Fork 430
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
Alsa module blocks when joining thread on destruction. #62
Comments
Hello, Thank you! |
I have this problem with version Here is my
|
You can also test with audio-loop (command "a"). Do you use a clean alsa or with pulseaudio? |
I tried the audio-loop command as you suggested, but I have no sound. It seems that pulseaudio is used when I use baresip; I don't know much regarding audio configuration, but based on this answer on Ask Ubuntu, I did grep the ouput of
I can try without PulseAudio but I have to find out how to disable it for Baresip first... The output of baresip when invoking audio-loop gives:
However, joining the thread does not block when quitting the application! |
I just tried audio-loop when running baresip without pulseaudio (using
|
With pulseaudio 6.0 on archlinux there is no such problem. You can check with "pavucontrol" which audio interface is mapped to baresip. Maybe I can check this with debian jessie and pulseaudio next week too. |
most likely the read thread is hanging here:
in blocking mode this function call will not return until there are samples in the buffer. could you try a couple of things:
in alsa_src.c:
I have seen similar bugs before, so most likely it is a ALSA API-usage error (i.e. baresip). NOTE: using non-blocking mode is not really an option as it consumes 100% cpu |
is there any more updates on this one? if not feel free to close the Issue. |
Hello,
I am trying Baresip on Linux Debian Jessie. I am trying to figure out how to have working sound when dialing SIP URI. Logs when dialing say:
The audio does not work in my case, so I quit (I type
q
); when doing that, the application hangs after dumping these lines:CPU takes 100% and I have to kill the process using
kill -9
. When running the application ingdb
, the following threads are running:And the backtrace of the current thread is:
This may be related to the fact that I have no sound (maybe a problem regarding NAT traversal?), but in any case joining the thread blocks the application.
The text was updated successfully, but these errors were encountered: