|
From: musikBear <mk...@ho...> - 2012-03-02 14:04:49
|
I have constantly hangs and occasionally i have real pc crashes where only resolution is a goofy-grip. These situations are the result of the LMMS 'autosave of the 'recover.mmp' file. I will illustrate the behavior with pictures from Task-manager. In this picture you can see how autosave causes enormous peaks in CPU usage. It also shows that autosave requires more CPU than a saving manually and saving manually during playback has the lowest cpu-usage (?) see this picture http://www.yourfilelink.com/get.php?fid=775478 pt 1 on the picture shows a manual save peak during playback. eg i pressed the 'save-file' during playback in the song-editor. Song-editor! Thats important! pt 3 shows a manual save-peak in idle state -eg the 'stop' was pressed and then the save button was pressed. pt 2 shows the peak that is a result of lmms' own auto-save. This peak is clearly seriously larger. It is both higer and extended over time. Crashes occur if something else is taking place on the pc at that moment. The autosave also block the opportunity to have 2 instances of lmms open simultanious, which can be pretty useful if for instance a drumpattern should be copied to a new project. I think saving to (uncompressed) .mmp takes more cpu than saving to mmpz (compressed) -but ..that is pretty irrelevant at least to me. What i strongly advocate is a way to disable the autosave ALL TOGETHER. The logic placement of this choice would be in the 'General Settings' -section. After having to restart several times i must say that i feel strongly for a resolution of this issue. The autosave to recover is not a feature -it is bug -a crash-prone bug even. ----- Hope this helped BR. --------------------- Tutorials and some music on : http://www.youtube.com/user/bearsoundz -- View this message in context: http://old.nabble.com/Serious-crash-problematic-code-in-LMMS-%27autosave-recover-the-project.-tp33428675p33428675.html Sent from the lmms-devel mailing list archive at Nabble.com. |