Crash in Brackets Editing Mode and on Save

• Mar 18, 2019 - 09:34
Reported version
3.0
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
MuseScore

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

Comments

• Mar 18, 2019 - 09:43
Status needs info ⇒ active

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...

Reply

• Mar 18, 2019 - 09:46
Status active ⇒ needs info

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

Reply

• Mar 18, 2019 - 10:17

"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)

Reply

• Mar 19, 2019 - 08:33

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.

Reply

• Mar 19, 2019 - 09:04

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?

Reply

• Mar 19, 2019 - 09:40

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"

Reply

Fix version
3.1.0