MS crashes after any change - not able to continue work
I am not able to continue work on a full score and parts that I have spent a lot of time on already.
Any change I make, be it in the full score or a part - the whole programme crashes.
It seems that the "save" command is what triggers the crash, not before that, at least not every time before that.
| Attachment | Size |
|---|---|
| Põldmäe, Alo - Siin oled kasvanud - LK, PK, SO koondpartituur - Tartu LP 2019 - M.L. gr.mscz | 71.63 KB |
Comments
Confirmed. Also crashes in latest development build.
It crashes with a failed assertion (latest master code self built in DEBUG mode):
Fatal: ASSERT: "first()" in file ...\MuseScore\libmscore\measure.cpp, line 1846
Thanks for confirming.
I will try to add relevant information if I know what to add.
First, I think it was started in MuseScore 2 - I see that I have delivered an early version of the full score (not having worked on parts yet) on February 26.
However, I have so far not had any troubles with this or any other file that have been started in the earlier version and continued in MS 3. Neither have I had any other trouble with MS 3 at all.
I have the folder synchronized with OneDrive and there seems to be a kind of version history service there, where I could restore 5 previous versions of the file.
In reply to Thanks for confirming. I… by lppoja
Any of those 5 previous version that does not crash on save? If so the newest that doesn't crash might be helpful for comparison.
Mind to file that in the issue tracker?
In reply to Any of those 5 previous… by Jojo-Schmitz
I will try and find one. Would I then have to file both files to that issue tracker?
In reply to I will try and find one… by lppoja
yes please, the last one that works and the first that fails please
I have now tried starting again from the last but one version, which still crashed the same way, though yesterday I had continued from that state by making a couple of new parts.
I have found a version that allowed some changes and saved without crashing and am attaching it here.
I am willing to file it in the issue tracker as well, but at the moment I am not sure whether I can fill that form correctly.
In reply to I have found a version that… by lppoja
don't worry, just fill it to your best effort, we'll take care of the rest ;-)
Edit: thanks for #287263: MS file began crashing after every save (orchestra and parts)
In reply to don't worry, just fill it to… by Jojo-Schmitz
I have filed it there now.
I may try to go on working from the previous version of the file, but I am not sure if I have time for that in the next couple of hours or even today, so I do not know yet whether I can report anything new about that very quickly.
Thank you and I will be following what can be found out in that comparison.
You wrote:
though yesterday I had continued from that state by making a couple of new parts.
So...
I took your original posted file, removed the parts, and it seems to be ok:
Põldmäe, Alo - Siin oled kasvanud -2.mscz
(Parts deleted, then score saved)
In reply to You wrote: though yesterday… by Jm6stringer
Thank you,
this may turn out to be very useful.
After starting work again from an earlier version (0.8), I found that the problem may have arisen in connection with what had happened in flute 1 and 2 in full score and in parts in bar 32.
When making parts, the application did not copy the notes of 32 to the flute 2, I wrote them manually in that part, and then a very strange picture with double notes appeared in the full score. Later, I was again trying to fix that, and the crash occurred then. However, after restart it got fixed when I deleted one note from Flute 1 line in the full score and then undid that move, after which there were some more minor graphic issues, but now the line looks good in both full score and parts. I hope I can keep going from here.
(The attached file is the latest now)
In reply to Thank you, this may turn out… by lppoja
This score is corrupt:
Measure 31, Staff 1 incomplete. Expected: 6/8; Found: 17/16
Measure 32, Staff 1, Voice 2 too long. Expected: 6/8; Found: 10/8