-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
LMMS process keeps running (master) #4668
Comments
Do you have a backtrace? |
Unfortunately it doesn't produce any traceback.
|
@karmux You can try |
Click to expand
|
I can reproduce this with SDL2. The hang happens randomly, but LMMS almost always hang when closing after loading |
Same problem for me, every time I close LMMS. Click to expand
Looks like thread 1 is waiting forever for thread 10 to finish:
Is there any additional information you need? |
After some investigation, I found some interesting facts.
However, I'm still not sure what can we do. |
As @wolfram-omega's backtrace shows, it's related to the audio capture thread. If I comment out the call to |
Ok, The problem is that SDL waits for the PulseAudio thread to exit but it won't quit for some reason. The strange thing is, that nothing is stuck on lmms side. I suspect it is an upstream bug. |
I found, that LMMS hung (on my Debian 10 system allways) on SDL destructor and with this "redaction"
LMMS not hung more ... |
Some more information: |
(1) Experimenting with SDL2 I found that one lag in |
Minimalistic change in Mixer.cpp ~303 line:
And now there is no lag - and SDL quit without problems ... Should I do PR? |
I think it is good idea. Any fix to lmms SDL perfomance will be good, as it is default backend in lmms. |
Thank You for answer! I'll make PR in 1 - 3 days . Key problem is - how to test? |
I think |
On master branch LMMS process keeps running after exit.
I just open and close LMMS without loading any project.
I'm using Manjaro Linux and SDL audio interface.
This doesn't happen in stable-1.2 branch.
Also this doesn't happen with PulseAudio in master branch.
gdb doesn't show anything useful.
The text was updated successfully, but these errors were encountered: