Crash opening score that works in version 2
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S1 - Blocker
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
The OpenScore Edition of Debussy's Deux arabesques works without issues in MuseScore 2 but opening it in MuseScore 3 gives a segmentation fault.
Other OpenScore Editions, such as this one, don't seem to cause a crash (though they are not imported entirely correctly).
Attachment | Size |
---|---|
Debussy_-_Deux_arabesques.mscz | 768.17 KB |
Comments
See https://github.com/musescore/MuseScore/pull/4304.
Fixed in branch master, commit f4d8604865
fix #279172: skip correctly if not handled on 2.X import
Fixed in branch master, commit 599c33eb0a
Merge pull request #4304 from dmitrio95/279172-read206-timestretch-crash
fix #279172: skip correctly if not handled on 2.X import
The fix allows the score to be opened once, but now it crashes on certain edits, and always on saving the score or attempting to re-open it.
If you choose not to reset positions then it allows you to save it and reopen it again, but it does eventually crash when you start making changes (even the newly saved version that's supposedly in version 3 format), so it seems it never quite makes it into the new file format for 3.
Edit: The above was true on macOS. On Linux I still can't open the file at all without a crash. Tested in latest nightly on both platforms (revision 55e0dae) .
Assertion failure on load in QList for me.
The first commit in PR 4346 fixes score loading for me. I noticed no crashes after saving/loading it again. Though I didn't make any substantial edits to the score so feel free to report any other problems if they are remaining.
Fixed in branch master, commit 69ba5de735
fix #279172, part 2: Detach beams from system on relayout
Fixed in branch master, commit aed2b3c41a
Merge pull request #4346 from dmitrio95/279172-debussy
fix #279172, fix #279448: fix two issues related to beams containing pointer to invalid system
Automatically closed -- issue fixed for 2 weeks with no activity.