Three different crashes
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
On a piano score, running MacPro 12cores. HighSierra
1) copy-paste 4 bars
2) Changing time signature
3) browsing menu
Attachment | Size |
---|---|
MS3 logs.zip | 71.47 KB |
Comments
Why not reproducible :)
Looking at the log I can reproduce the first one:
1) Open the attached score.
2) Select the first measure.
3) Copy (Ctrl+C).
4) Select the 4th measure (that one with many notes).
5) Paste (Ctrl+V).
And it really crashes with a similar stack trace.
The third one looks like this known MacOS-specific problem: #278772: [MacOSX] Crashes randomly when go to do any menu item.
Concerning the second one I am not sure how this can be reproduced. Could you please describe approximately some actions you did when you got that crash with adding a time signature: which signatures did you try to change, was that somewhere in the middle or in the end of the score, were there some other time signature changes in that score? Maybe this could give us some hints on how to reproduce the issue.
I am marking this as P0 for the crash though we should perhaps also file some separate bug report for the second issue and change the name for this one.
In reply to Why not reproducible :)… by dmitrio95
Well, not reproducible cos after having relaunched MS3 I could copy and paste easily, cos I've added a 4/4 bar on a 3/4 score like I was trying to do when it crashed, and cos I could browse all the new MS3 menu without problems.
Copy-paste issue should be fixed by https://github.com/musescore/MuseScore/pull/4346.
Concerning time signature change issue I managed to reproduce some crashes on changing time signatures but these seem to be not exactly the same case, see #279593: Crash on changing time signature.
Fixed in branch master, commit 7664bcf4f5
fix #279448: deselect all elements on planning a delayed selection
This way selection will avoid containing elements that have pointers
to invalid elements (e.g. systems deleted 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.