Creating part causes crash
when i want to create differentes parties of one song, musescore fails and shut down. This is wat then appears:
Probleemhandtekening:
Gebeurtenisnaam van probleem: APPCRASH
Naam van de toepassing: mscore.exe
Versie van toepassing: 0.0.0.0
Tijdstempel van toepassing: 4e301be1
Naam van foutmodule: mscore.exe
Versie van foutmodule: 0.0.0.0
Tijdstempel van foutmodule: 4e301be1
Uitzonderingscode: c0000005
Uitzonderingsmarge: 0005e17a
Versie van besturingssysteem: 6.1.7600.2.0.0.768.3
Landinstelling-id: 2067
Aanvullende informatie 1: 0a9e
Aanvullende informatie 2: 0a9e372d3b4ad19135b953a78882e789
Aanvullende informatie 3: 0a9e
Aanvullende informatie 4: 0a9e372d3b4ad19135b953a78882e789
Comments
What operating system and version, what MuseScore version, can you attach the score that causes the problem?
What are the exact steps to reproduce the crash you see?
operating system: windows 7
musescore version: 1.1
i open the song witch contains 4 parties. then i try to create separate pages for soprano, alto, tenor and bass. (bestand, partijen, nieuw, creëer partij) Then the system turns pale en i get the following report:
Probleemhandtekening:
Gebeurtenisnaam van probleem: APPCRASH
Naam van de toepassing: mscore.exe
Versie van toepassing: 0.0.0.0
Tijdstempel van toepassing: 4e301be1
Naam van foutmodule: mscore.exe
Versie van foutmodule: 0.0.0.0
Tijdstempel van foutmodule: 4e301be1
Uitzonderingscode: c0000005
Uitzonderingsmarge: 0005e17a
Versie van besturingssysteem: 6.1.7600.2.0.0.768.3
Landinstelling-id: 2067
Aanvullende informatie 1: 0a9e
Aanvullende informatie 2: 0a9e372d3b4ad19135b953a78882e789
Aanvullende informatie 3: 0a9e
Aanvullende informatie 4: 0a9e372d3b4ad19135b953a78882e789
This score crashes both 1.1 (R4897) and 2.0 (R4900) when doing parts. I do notice some score corruption starting in bar 33 (key change?). The key change (naturals) start on every system after that.
I changed bar 33 and IT WORKS. Thank you very much :)
So there are actually 2 issue here: a) MuseScore shouldn't crash on this and b) MuseScore shouldn't have corrupted the score in the first place.
What should we do now?
The corrupted score (bad key signature) can be read in r4910 (the bad key sig is skipped). The trunk implementation is different so i believe the cause of the corruption is already fixed.
r4910 is trunk, not branch, isn't it?
Yes, a trunk fix only (so far).
I understood werner that the trunk had id fixed since long?
Ah, I see: the casue fro the corruption got fixed long ago, the ability to read a corrupted scrore just now.
OK then...
I ported the fix to the branch in r4911
Automatically closed -- issue fixed for 2 weeks with no activity.