mscore 2.0.0 Rev 58ee008 -- segmentation fault

• Jan 18, 2013 - 01:25

System is OpenSuSe -- 12.2 x-64 architecture
Qt rev 4.8.4

Downloaded from github and compiled/installed

program loads fine

create new score, piano, bass clef removed. The empty score looks good.

click on 'N', add an 'E' note by pressing E

click on 'N' to end insert

click 'File -> save as'

accept suggested filename

Segmentation Fault

*** Note: there was no information on the segmentation fault. ***

Output from program attached.

Attachment Size
mscorelog.txt 235 bytes

Comments

• Jan 18, 2013 - 13:33

From further investigation..

1. After the crash, the file that was being saved does appear in the directory, but as a zero length file. Creating more notes still leaves a zero length file. mscore will not reload the file.

2. And probably more important, if I create the new score as piano with both treble AND base clefs, then the file is saved correctly and mscore does reload it.

Methinks there is a problem with having deleted the base clef.

Anything I can do to get further into the problem?

Reply

• Jan 18, 2013 - 14:21

Jojo,

in the dialogue to create the initial script, I select:

Keyboard -> piano

Then in the right hand window I select the bass clef and click on remove so only the G clef remains.

I then click finish.

If this files is saved, them mscore crashes.

If, when I create a score, I do not delete the bass clef, (i.e leave the bass clef and treble clef) then the score can be saved without problem.

Creating a score with single treble clef for example a violin, also works.

It looks like the problem has something to do with removing the bass clef from a piano, on creating the score and then later saving it.

Reply

• Jan 18, 2013 - 14:27

I used the latest build as requested yesterday by chen lung:

Submitted by chen lung on January 17, 2013 - 4:56pm.
Hi

I can't reproduce - what operating system are you using?

The commit you are using is from last week - could you try the latest?

https://github.com/musescore/MuseScore/commits

Thanks :).

Using MuseScore 2.0 Nightly Build (58ee008) - Mac 10.7.5.

I went to the nightly build you pointed me to and the latest is over a week old.

Reply

• Jan 18, 2013 - 14:43

From what have seen in the trunk, there have been major changes regarding saving/loading XML. This affects a lot. The first major change was Jan 11, and the rest were yesterday (Jan 17) and today (Jan 18). Hopefully the fixes required for this change are almost done but until then XML might be broken.

Reply

• Jan 18, 2013 - 15:00

In the create score dialogue, having first selected the Instrument 'piano', under the heading 'Staves' in the right hand window, I have initially:

Piano
staff 1 Treble clef
staff2 Bass clef

I click on the line 'Staff 2' to select it,

Then click on 'Remove', the button to the left.

I then click on 'finish;.

This then gives me a score with only the treble staff. This is the score which causes the seg. fault.

Reply

Do you still have an unanswered question? Please log in first to post your question.