MuseScore .95 appears to run memory leak, slows then crash on long score
My stepson ran into this problem on windows xp a few days ago.
1. He was working on a score writing parts for several instruments when MuseScore began slowing down, response time slowed until the app crashed.
2. There was a specific number of measures reached when this happened.
NOTE: Will update this issue this evening 10-Feb-2010 with more details and probably a copy of the file he was working on that generated the problem.
Comments
He just showed me the issue he is having with .95 musescore version.
Score file is now included.
Windows XP - 2 gigs of ram. SP3
1. writing a score with eight instruments.
2. believe he created it with 140 measures.
3. at around 45- 50 measures adding notes or copying measures slows down considerably.
4. he said as you continue to try to add notes or copy measures the application stops working.
5. messege comes up saying the application now has to quit.
Hi David,
Updated bug with more info and attached the files he was working on.
Hope this helps,
Rob
I didn't get a crash but I can confirm that the score was very slugish.
I noticed that there were some corrupted measures at the end of the score. I deleted them and now the score is much snappier (see attached).
If you discover the exact steps that cause the measures to become corrupt please post them. Several of these issues have been addressed for the upcoming release of MuseScore.