Opening a part causes crash

• Oct 3, 2011 - 20:17
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

1. Open a score with a part.
2. Click on part.

Result: Crash.

Using MuseScore 2.0 Nightly Build (4832) - Mac 10.6.8.

Thanks to shutterfreak .

Comments

• Oct 3, 2011 - 23:32

I think I identified the root cause. The tabs are displayed even if the parts must still be created (via File → Parts → Create). The crash is gone if I create a part this way and then click on the part's tab.

Probably a NULL pointer issue (part not yet created).

Reply

• Oct 4, 2011 - 00:51

I should have actually looked into it more :).

I'm a bit puzzled as to how that score was created (with regards to parts). Can you take us through it?

Reply

• Oct 4, 2011 - 06:49

I first created the score, then I defined 6 parts (1 per instrument + 1 for the 2 violins + 1 for the viola & cello).

In MuseScore 1.1 you have to generate the parts as they're not shown otherwise. There's even no link between a score and parts thereof in MuseScore 1.1.

With MuseScore 2.0 nightly I see it understands that there are parts in the score as I get 2 rows with tabs: the score and below it the individual parts of that score. Since I imported an existing score into MuseScore 2.0 nightly the individual parts did not exist on disk yet.

Instead of crashing, MuseScore 2 should either create the parts or warn the user that the part does not exist and offer the following 2 options: create the missing part from the master score, or search for the part on the file system.

Reply