RemoteVst still running after LMMS exit

[DaAwesomeP]

They were taking up RAM. I noticed this in Task Manager. There were quite a few of them - one for each of the VSTs I had open in vestige in the most recent project. I had to force quit them.

Windows 8 Pro 32-bit

[tresf]

A proper report should have the exact steps to reproduce every time please.

Zombie processes would normally occur when the VST crashed. If it is happening during normal usage, we need to know why, and the steps to reproduce may help us understand that.

[musikBear]

No, this has been up before. If you DaAwesomeP search this board, you will find an identical issue. The poster also had an 'orphan' but the reason was that he had terminated the vst in a wrong way.
All remoteProcessVST are shut down and removed correctly, IF lmms is closed properly.
Some vst-effects creates orphans, but thats because they cant run in lmms, and craches, without crashing lmms (zasfx can do the same, but i doubt it 'our' bug -but something 'we' do need to take up the the zyn-group)

[Sti2nd]

The bug goes like this: If you press on the x, to close the VST window, you will get those VeSTige instances after you quit LMMS. If you use the big button "Show GUI" to also close the VST window, you will not. I am not sure if this was made because of any logic, or if it is just a bug.

[DaAwesomeP]

Show I need to press "Hide" before I close LMMS? I wasnt clicking the X on the VST windows, just LMMS as a whole. 

-------- Original message --------

From: Stian Jørgensrud [email protected]

Date:09/29/2014 11:27 AM (GMT-06:00)

To: LMMS/lmms [email protected]

Cc: P THE AWESOME [email protected]

Subject: Re: [lmms] RemoteVst still running after LMMS exit (#1182)

The bug goes like this: If you press on the x, to close the VST window, you will get those VeSTige instances after you quit LMMS. If you use the big button "Show GUI" to also close the VST window, you will not. I am not sure if this was made because of any logic, or if it is just a bug.

—
Reply to this email directly or view it on GitHub.

[Sti2nd]

I have read and experienced myself that the VSTs mostly hang on my system when one don't use the Show/Hide GUI button in LMMS. I don't know if having some of the GUI's open when closing LMMS also won't kill the process, but you could try.

[SecondFlight]

I didn't know this wasn't a known issue. This happens to me every time I'm using VSTs in a project.
I did my research - turns out it is a known issue :3

[DaAwesomeP]

I should note that I'm using mostly Native Instruments VSTs. I don't know if this happens with the LADSPA effect VSTs as well, I've only needed to use VesTiGe since I started using LMMS.

[SecondFlight]

the LADSPA effect VSTs

LADSPA is a plugin format, and so is VST. If it says LADSPA in front of it, it is a LADSPA effect, and vice versa.

[musikBear]

in respect to the orphans. This is fixed. The 1.1 to come will not create orphans. Further more: The 'x' for closing is removed. This is however not a idiot-secure feature-change, because you can still right-click, and from the contex choose 'close' -BUT!
Even if that is done, when lmms is properly closed, it will close the remoteVstprocess!
These vere fine changes is for instruments! Effects is another, and sadly more murky area. Where failing vst-instruments actually fails rather obvious, and gives the user ok information, failing effects can do this silent, and without the user notice that the process is not working. Right now,vst effects are not stable supported. (imo) - It would be an absolutely amazing addon, if the ladspa contained zasfx standalone effects, could be ported to lmms. Without doubts the best effect collection, and 👊 all vst-effects i have tried, including blue-cat -whitch comes second

[tresf]

@musikBear, when you claim these bugs are fixed, can you link the commit or duplicate bug report which closes it? If this is fixed in 1.1, this bug report should also be closed.

[Sti2nd]

Indeed, cause the "fix" you are referring to (which I have also seen) does sound awfully lot as a workaround.

[musikBear]

@tresf , no i dont know whitch commit that fixed it 👎 -But i just cant create orphans woth 1.0.95 (rc 5 i believe, but its not added to the release.. so (ple..ase do that.. its so futile and time wasting that we dont know exact what rc's we mess around with))
I get orphans if i delibrately crashes lmms, or kill it from taskMan, but -again- that is instruments only!!
vstEffects will create orphans, if they fail
(gues thats where the orr opp got the orphan??)
(btw , the missing 'x' is not consistant, some vst still have it (Crystal a. e.) I do not know why

[zonkmachine]

I close this bug as a duplicate of #2774

[lukas-w]

@zonkmachine I think these are separate issues. #2774 is about lmms.exe still running after exit, while this one is about RemoteVstPlugin.exe still running.

[DomClark]

I'm closing this as a duplicate of #4408 as that issue has more recent discussion and a proposed fix.