RemoteVstPlugin becomes a zombie after crash

[sakertooth]

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 terminate wineserver. I'm unsure as to whether or not the way LMMS crashes influences this bug.

Steps to reproduce

1. Create a project that has some third-party plugin as an effect on one of the mixer channels.
2. 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.

[sakertooth]

Thankfully, getting LMMS to crash does not have to be done in a specific manner, as this bug can still occur by sending a SIGKILL signal to LMMS.

[Gumichan01]

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.

[SpomJ]

Mem usage is fine, after lmms failed to load a vst 4 times in a row (wine issues probably), mine CPU was officially dead...