The crash happens at line 3629 of layout.cpp. Apparently, m->system() is 0 for the part score (i.e. not the masterScore). Attached log file from AddressSanitizer.
I also found the reason why there's no crash if the score is created from scratch:
If a score is loaded and edited, for each part Score::doLayoutRange() is called and crashes for parts that have a multi measure rest.
If the score is newly created, Score::doLayoutRange() is only called for the master score, that doesn't have the multi measure rest as default. For the parts Score::doLayout() is called and no crash happens.
If you enable multi measure rests in the master score before editing it, it will also crash with a newly created score.
Comments
The crash happens at line 3629 of layout.cpp. Apparently, m->system() is 0 for the part score (i.e. not the masterScore). Attached log file from AddressSanitizer.
Commit e1065347
Linux Mint 17.3
Interestingly, it works ok with a score created from scratch
I think this is the same problem that caused #117766: Crash when editing first measure of loaded score with multi measure rests
So we might mark this as a duplicate?
Since PR 2733 fixes this, I mark it as duplicate of #117766: Crash when editing first measure of loaded score with multi measure rests
I also found the reason why there's no crash if the score is created from scratch:
If a score is loaded and edited, for each part Score::doLayoutRange() is called and crashes for parts that have a multi measure rest.
If the score is newly created, Score::doLayoutRange() is only called for the master score, that doesn't have the multi measure rest as default. For the parts Score::doLayout() is called and no crash happens.
If you enable multi measure rests in the master score before editing it, it will also crash with a newly created score.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.