You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When LMMS crashes, the RemoteVstPlugin's do not exit and become zombie processes. To make matters worse, the memory usage seems to slowly trickle up after some time, with the only solution being to terminate wineserver. I'm unsure as to whether or not the way LMMS crashes influences this bug.
Steps to reproduce
Create a project that has some third-party plugin as an effect on one of the mixer channels.
Get LMMS to crash (can be done by sending the SIGKILL signal to LMMS).
Expected behavior
Once LMMS crashes, the RemoteVstPlugin processes should close, and the memory should not slowly increase over time.
Actual behavior
Once LMMS crashes, the RemoteVstPlugin process stays open and the memory usage slowly increases over time.
Affected LMMS versions
Unsure.
The text was updated successfully, but these errors were encountered:
I assume you are using LMMS on a Linux distribution.
I have a similar issue on Windows in several projects that use VST plugins with LMMS 1.2.2. It could be interesting to reproduce in the alpha version to check if this was fixed.
Bug Summary
When LMMS crashes, the
RemoteVstPlugin
's do not exit and become zombie processes. To make matters worse, the memory usage seems to slowly trickle up after some time, with the only solution being to terminatewineserver
. I'm unsure as to whether or not the way LMMS crashes influences this bug.Steps to reproduce
SIGKILL
signal to LMMS).Expected behavior
Once LMMS crashes, the
RemoteVstPlugin
processes should close, and the memory should not slowly increase over time.Actual behavior
Once LMMS crashes, the
RemoteVstPlugin
process stays open and the memory usage slowly increases over time.Affected LMMS versions
Unsure.
The text was updated successfully, but these errors were encountered: