Thu Oct 24, 2019 12:41 am
I've been trying to figure this one out and I see some similarities to this thread, but it isn't quite the same: https://lmms.io/forum/viewtopic.php?f=7 ... ash#p64302.
I'm not on Ubuntu or Mint, but rather Debian Testing which they're both derivatives of.
Long story short: I've been working on a project for about a week now that has 3 VST plugins: JM-1 Linndrum replica, ZASFX, and SQ8L. About halfway through the project, it started to become very unstable and freeze/crash LMMS with CPU pegged to 100% for that process.
I think it might be somehow related to the drawing curves in Xorg because things were pretty solid until I starting adding automation tracks and drawing out volume changes in the editor, but the real kicker came as the song grew and I had to start moving and copying/pasting these tracks and has since started happening when editing/moving the other tracks as well. I always know when the issue is about to occur because while copying/pasting a piano roll, the timestamp popup will suddenly stop and nothing except the main toolbar will respond; if I'm quick enough, I can squeeze in another save before full lockup. This does not kick me all the way back to a login screen as on Ubuntu or Mint, but it does render LMMS completely unresponsive. I then have to manually force-close LMMS, and the VST plugins appear in the taskbar as WINE processes that won't close without a logout/login of my desktop environment (KDE Plasma). I think it may be related to a memory issue because subsequent crashes occur more often throughout the session until I'm ultimately forced to restart. Another odd behavior is that when I started the project, loading it also brought up the consoles of the VSTs; came up in the background workspace along with the song editor, FX Mixer, etc. but now they don't.
I'd appreciate any help figuring this out, it can be real disruptive if I'm in a flow when it happens. Also, does anyone who's working in Linux know if the Xorg patch mentioned in the link is available outside of the normal update channels to be applied manually? I should have it in Testing at this point, but want to double-check and make sure by manually installing.
I'm not on Ubuntu or Mint, but rather Debian Testing which they're both derivatives of.
Long story short: I've been working on a project for about a week now that has 3 VST plugins: JM-1 Linndrum replica, ZASFX, and SQ8L. About halfway through the project, it started to become very unstable and freeze/crash LMMS with CPU pegged to 100% for that process.
I think it might be somehow related to the drawing curves in Xorg because things were pretty solid until I starting adding automation tracks and drawing out volume changes in the editor, but the real kicker came as the song grew and I had to start moving and copying/pasting these tracks and has since started happening when editing/moving the other tracks as well. I always know when the issue is about to occur because while copying/pasting a piano roll, the timestamp popup will suddenly stop and nothing except the main toolbar will respond; if I'm quick enough, I can squeeze in another save before full lockup. This does not kick me all the way back to a login screen as on Ubuntu or Mint, but it does render LMMS completely unresponsive. I then have to manually force-close LMMS, and the VST plugins appear in the taskbar as WINE processes that won't close without a logout/login of my desktop environment (KDE Plasma). I think it may be related to a memory issue because subsequent crashes occur more often throughout the session until I'm ultimately forced to restart. Another odd behavior is that when I started the project, loading it also brought up the consoles of the VSTs; came up in the background workspace along with the song editor, FX Mixer, etc. but now they don't.
I'd appreciate any help figuring this out, it can be real disruptive if I'm in a flow when it happens. Also, does anyone who's working in Linux know if the Xorg patch mentioned in the link is available outside of the normal update channels to be applied manually? I should have it in Testing at this point, but want to double-check and make sure by manually installing.
