Crash in Brackets Editing Mode and on Save
Reported version
3.0
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
OS: Windows 7 SP 1 (6.1), Arch.: x86_64, MuseScore version (64-bit): 3.0.5.5992, revision: 58dd23d
1) Load this file (Grand staff Template): Grand staff1.mscz
2) Double-click Bracket (for edit mode)
3) Save (Ctrl + S)
-----> Crash
Fix version
3.1.0
Comments
I can't reproduce, same OS, same version of MuseScore
I can when actually changing the bracket (making it longer and without leaving edit mode), so
Step 2.5. Change length of bracket
Crash report sent.
Hmm, seems step 2.5 is not always needed...
Try this:
1) Create new score: eg Grand Staff template
2) Save as... -> New name -> Save
3) Double-click the bracket
4) Save (Ctrl + S)
-----> Crash
"Crash report sent"
And so, at some point, we're going to have to know what it's useful to do. If the crash report is made with the new automatic tool, (report facility), should it be done again on this Issue Tracker?
Either it is simply considered as a useless duplicate, or this Issue Tracker simply becomes irrelevant (at least as far as crashes are concerned)
From my experience, crash reports are really useful for those issues that do not have such a reliable way to reproduce them, or to learn about some issues that are not known to the issue tracker yet or are reproducible in rare cases (like a crash in 3.0.3 on 1.X scores with a specific tag that was not used by almost all scores I could find). In case there is a detailed report in the issue tracker with the reproduction steps the crash reports become less relevant as all the information they may contain (OS, call stack trace, approximate context description by a user) is already contained in the issue tracker report.
Okay, I kind of understand, but kind of, sorry, I'm not a developer alas. And I'm still wondering what the general recommendation might be right now for these bug reports in the Issue Tracker.
Let's start with an example, this one precisely: is this report in the Issue Tracker about brackets edition on Save useful for you? Or not at all?
It is very useful, of course. As I mentioned above, having precise steps to reproduce an issue is always very helpful, and that is what cannot be provided by most crash reports.
By the way, here is a pull request to fix the issue:
https://github.com/musescore/MuseScore/pull/4811
Okay. thanks. For the record, I notice that the crash, at the last step, occurs with the shortcut (Ctrl + S), but not via the menu "File" -> click "Save"
Fixed in branch master, commit db0ebb5bd8
fix #286240: fix a crash on score save when editing a bracket
Fixed in branch master, commit 36765c41c8
_Merge pull request #4811 from dmitrio95/286240-bracket-edit-save-crash
fix #286240: fix a crash on score save when editing a bracket_
Automatically closed -- issue fixed for 2 weeks with no activity.