Assertion failure when opening a file from MuseScore 2.X
Reported version
3.0
Priority
P1 - High
Type
Functional
Severity
S1 - Blocker
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
For reproducing try opening the following file:
https://musescore.org/sites/musescore.org/files/issues/Bidonville_5_1.m…
Backtrace is attached below.
The file was originally found in this bug report:
#89106: hang/crash when saving and reopening attached file
OS: Debian GNU/Linux 9 (stretch), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: b3feb3a
| Attachment | Size |
|---|---|
| backtrace.txt | 3.36 KB |
Comments
It seems I forgot to change the status of the issue, the pull request was created: https://github.com/musescore/MuseScore/pull/4090
And this does not affect the release version, and the file is really corrupted. Given that I believe we can mark it with a bit lower priority if this still matters.
Fixed in branch master, commit 2e93de1993
fix #276969: relink staff if multiple tags are read
This does not guarantee that the file will be read correctly
but this prevents assertion failure and possible memory leaks
on subsequent ScoreElement::linkTo call
Fixed in branch master, commit 752bbb4e97
Merge pull request #4090 from dmitrio95/276969-multiple-linkedto
fix #276969: relink staff if multiple tags are read
Automatically closed -- issue fixed for 2 weeks with no activity.