This thing was introduced in the rc-5 version of LMMS I have if I know. I'm not sure if this is the true reason of the unpredictable freezes though when I knew it was added in rc-5, I was thinking it is the culprit.
When I'm editing an automation or note patterns (loop) while the song is playing, the CPU usage becomes high which can be also triggered by moving the cursor quickly. And, adding a LADSPA effect is pain in the ass and causes LMMS to stop for a while if you insert one for the first time after restart as it has to load them in memory (and, in my hypothesis, they aren't loaded in the memory in the start up.) Playing the metronome for the first time after restart also freezes LMMS for few seconds (then returns to normal) when a project is playing the song. Loading big projects (like the extended mix of my trance song Night Shift that has 800-1K objects in the Song Editor) loads 3-5 minutes. One thing is, this doesn't happen in the 1.1.3 I have installed. And loads Night Shift for less than 10 seconds (but sometimes the automation tracks disappear, this is an old problem.)
I may have a really old PC lol, but... why 1.1.3 looks more stable at this point? Yes, it's 'unstable release' but I've read in a forum post here that comparing the two 1.1.3 is less stable now than rc-5. Looks like it doesn't happen for me. The memory manager is likely to remove things that weren't probably be used by the user at restart to reduce unused objects that can save memory, but there would be a problem when it loads into RAM, especially when a song is playing/note pattern is playing notes, or caught in a bad luck that LMMS crashed and froze just because of loading the codes and objects. Example, the LADSPA plugins list. It won't load into memory unless opened by the user in "Add effects". Then, dragging samples. Idk why it lags, though not all of the samples (or even none of them) were loaded into memory. Also the metronome, mentioned on the previous paragraph (in that case, a song was playing.)
I hope, in the next release, if the memory manager is really causing these problems, I suggest that there would be settings on it [that require restart], like un/redo steps, what should be and shouldn't be loaded into memory at restart or while LMMS is running or if should it be enabled or disabled, and some advanced settings because even importing samples from the left dock freezes LMMS a little
When I'm editing an automation or note patterns (loop) while the song is playing, the CPU usage becomes high which can be also triggered by moving the cursor quickly. And, adding a LADSPA effect is pain in the ass and causes LMMS to stop for a while if you insert one for the first time after restart as it has to load them in memory (and, in my hypothesis, they aren't loaded in the memory in the start up.) Playing the metronome for the first time after restart also freezes LMMS for few seconds (then returns to normal) when a project is playing the song. Loading big projects (like the extended mix of my trance song Night Shift that has 800-1K objects in the Song Editor) loads 3-5 minutes. One thing is, this doesn't happen in the 1.1.3 I have installed. And loads Night Shift for less than 10 seconds (but sometimes the automation tracks disappear, this is an old problem.)
I may have a really old PC lol, but... why 1.1.3 looks more stable at this point? Yes, it's 'unstable release' but I've read in a forum post here that comparing the two 1.1.3 is less stable now than rc-5. Looks like it doesn't happen for me. The memory manager is likely to remove things that weren't probably be used by the user at restart to reduce unused objects that can save memory, but there would be a problem when it loads into RAM, especially when a song is playing/note pattern is playing notes, or caught in a bad luck that LMMS crashed and froze just because of loading the codes and objects. Example, the LADSPA plugins list. It won't load into memory unless opened by the user in "Add effects". Then, dragging samples. Idk why it lags, though not all of the samples (or even none of them) were loaded into memory. Also the metronome, mentioned on the previous paragraph (in that case, a song was playing.)
I hope, in the next release, if the memory manager is really causing these problems, I suggest that there would be settings on it [that require restart], like un/redo steps, what should be and shouldn't be loaded into memory at restart or while LMMS is running or if should it be enabled or disabled, and some advanced settings because even importing samples from the left dock freezes LMMS a little