Score that crashes MuseScore 2.0 beta 1
I find that the attached score reliably crashes mscore 2.0 beta 1.
I am using Mac OS X Mavericks 10.9.4 on a MacBook Pro 2.53 GHz Intel Core 2 Duo, 4GB 1067 MHz DDR3.
Opening it might make MuseScore hang. Trying to edit it (I was trying to change the chords in bars 22-23) will cause a crash.
I've also attached the Mac crash report.
Attachment | Size |
---|---|
Falling (Vocal).mscz | 5.71 KB |
mscore2-1crash201408311816.txt | 54.53 KB |
Comments
I have a feeling this may be connected to this #31506: Selecting second voice note head with lyrics causes crash which has already been fixed. I could be wrong.
Could well be. The is no way the issue with lyrics could cause a hang on load, but it could cause a crash with the log shown if you happened to select the "wrong" note. Selecting the pickup or first note of the main melody should be fine, selecting the second would crash in beta. Same with a number of other notes (second note of second measure, etc. Any note that has a "hole" in the lyrics - a place where there is a syllable for some voice but not the voice above. And indeed, already fixed in the development builds.
So if that appears to explain everything, we can close this. If you do see hangs on load, though, that is worth investigating further.
Is there a more recent build I can try, or do I assume you have done that so this can be closed to your satisfaction. I can always wait for beta 2.
Nightly's are the most recent you can get. You can try with that.
Just tried installing the latest nightly MuseScoreNightly-2014-08-30-0941-244f40d.dmg but it simply crashes and won't start.
Try the next, MuseScoreNightly-2014-09-01-1835-dbac0f2.dmg
And it it still crashes, try a factory reset first
I just tried with dbac0f284e on mac and can't reproduce. Looking at the crash report is indeed look similar to #31506: Selecting second voice note head with lyrics causes crash. I put it on fixed. Reopen if needed.
Neither of those builds are on the OS X list, but I'm happy for you to have marked it fixed if you have tested it.
Thanks.
Automatically closed -- issue fixed for 2 weeks with no activity.