Adding a tie crashes Musescore 4.0.1
Reported version
4.0
Type
Functional
Frequency
Few
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
1) Open file titled "P - copy.mscz"
2) Scroll over to measure 63 (two measures before rehearsal number 5)
3) Scroll down on the score to the second line of the Flugelhorn part and click on the empty measure
4) Insert any note, no greater than a half note in duration
5) Insert a second note after the one in the previous step (again, no greater than a half note)
6) Tie the two notes together
Expected behavior: A tie will be added
Actual behavior: Musescore will buffer for a few seconds and crash
OS: Windows 10 Version 2009, Arch.: x86_64,
MuseScore version: 4.0.1-230121751, revision 9b70a8c
Note: This score is a transcription of a work in the public domain
Attachment | Size |
---|---|
P - copy.mscz | 118.88 KB |
Fix version
4.0.2
Comments
In reply to Measure 63 at the 2nd line… by Jojo-Schmitz
I'm looking at the score right now and measure 63 of the second line of the flugelhorn part is completely empty. When I try to tie two notes of the same pitch, Musescore crashes.
Additionally, my original score (I originally attached a copy, I couldn't figure out how to attach a score saved on the cloud. The problem with the ties is present in the copy as well) is now corrupted, which wasn't the case when I originally posted this.
If you don't attach the score that shows the issue, we can't analyze it.
In reply to If you don't attchat the… by Jojo-Schmitz
I did.
? But with that score I can't reproduce, see above
In reply to ? But with that score I can… by Jojo-Schmitz
That's the score I'm having issues with, see above.
It's been almost two weeks and I'm still having this problem, are the developers still working on finding a solution?
I can't reprodure, not with a 4.0.2 pre-release
I tried reproducing it and MuseScore crashed for me as well. The measure is empty.
Can you reproduce with a current nightly build?
Doesn't crash with current nightly build as far as I can tell.
Then let's mark it fixed
In reply to Then let's mark it fixed by Jojo-Schmitz
Issue was resolved in the latest update
Automatically closed -- issue fixed for 2 weeks with no activity.