-
Notifications
You must be signed in to change notification settings - Fork 90
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
stream.close() hangs #165
Comments
I think I found the issue. The auidio stream was being started by a thread and terminated by another. The Linux build didn't complain, but it was easily spotted by running the code on Windows (library warns loudly!). Doing start/stop in the same thread appears to fix the problem. Sorry for the inconvenience, thanks anyway! |
I may have spoken too soon. Got the problem again, within same thread. Still investigating. |
@norru any updates? only a few years later :D |
You probably don't need help with this anymore as it's been several years, but I came across a similar situation and I was able to solve it. I was holding the stream object, along with other stuff, all under the same mutex. So I had to lock the mutex to call Mine is probably a bad design, but I was able to solve it by simply replacing |
Hello, stream.close() for non blocking streams occasionally hangs. I have only seen it happen when the code is not optimized, usually after many buffer xrun. Haven't seen happening in
--release
builds (no xrun).I'm running the entire audio system in a separate thread, if it helps.
Here's the stack trace for all running threads:
The text was updated successfully, but these errors were encountered: