Assertion failure on trying to insert Figured Bass in debug build of MuseScore

• Oct 9, 2018 - 10:34
Reported version
3.0
Type
Functional
Severity
S3 - Major
Status
closed
Regression
No
Workaround
No
Project

Steps to reproduce:
1. Create a new score.
2. Put a note to the score.
3. Select a note.
4. Press Ctrl+G.
MuseScore crashes.

This bug prevented me from testing another bug report so it should probably be checked too after this one is fixed.
#75106: Crash With Figured Bass

Tested on:
OS: Debian GNU/Linux 9 (stretch), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: b3feb3a


Comments

Status (old) active needs info
Status active needs info

I can't reproduce here with the current 3.0 dev. :
OS: Windows 7 SP 1 (6.1), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: b3feb3a

That is interesting. Well, let's clarify a bit: if you open this score, select the only note in it and press Ctrl+G, it doesn't crash?

Attachment Size
test.mscz 6.63 KB

"Well, let's clarify a bit: if you open this score, select the only note in it and press Ctrl+G, it doesn't crash?"
Always not.
See:
bg.jpg bg1.jpg

I guess I know why you don't experience a crash — you are probably testing it on a release build! For me this assertion is failing, and it is not included in release builds. When I remove this assertion my debug build stops to fail on pressing Ctrl+G too.

"you are probably testing it on a release build!"
Exactly, as always.
For the record, it's not the first time there is a difference between release build vs. self build.

Title Crash on trying to insert Figured Bass Assertion failure on trying to insert Figured Bass in debug build of MuseScore
Severity S2 - Critical S4 - Minor
Status (old) needs info active
Status needs info active

Well, as we know now that this happens only in debug builds the issue should probably be considered not critical. Still I believe we will need to look at it some time — those assertions are usually added for some purpose.