Crash problem
I am writing an orchestral score and it has started crashing every time I try to save it.
I've enclosed the file.
| Attachment | Size |
|---|---|
| Suite Sunderland.mscz | 130.48 KB |
Do you still have an unanswered question? Please log in first to post your question.
Comments
Just to add, I am using Musescore 3.6 with Linux "Zorin". Only the enclosed file is affected.
In reply to Just to add, I am using… by phil_j
Doesn't crash for me, MuseScore 3.6.2, Windows 10.
Are you using the AppImage or something else?
In reply to Doesn't crash for me,… by Jojo-Schmitz
Hi, thanks for the reply.
I've now tried it on my laptop with the same problems, which leads me to believe that it is this particular file. Have you played the file all the way through? For me, it crashes at random places and it won't save as itself or as another file. I have tried playing, and saving, other files with no problems. The application isn't an Appimage.
In reply to Hi, thanks for the reply. I… by phil_j
I tried to save it, which in the initial post you claimed to be crashing
In reply to Hi, thanks for the reply. I… by phil_j
I've now played it too, still no crash
In reply to Just to add, I am using… by phil_j
Works OK for me on OS: Ubuntu 21.04, Arch.: x86_64, MuseScore version (64-bit): 3.6.2.548021370, revision: 3224f34. Qt version 5.9.8
You could try deleting the Parts and then see if that fixes it. If not, try the AppImage as Zorin might be lacking a QT feature or a lib. file.
In reply to Works OK for me on OS:… by underquark
Hi. Thanks for your reply, I'm going to try deleting the parts and I'll let you know if that solves it. I'm disinclined to try an Appimage, as the application is running fine with everything else.
In reply to Hi. Thanks for your reply, I… by phil_j
Only the AppImage is supported here, for packages form some Linux distribution you'd need to go to their maintainers.
In reply to Hi. Thanks for your reply, I… by phil_j
Actually I found the problem: your version apparently got built in Debug mode and crashed on a failed assertion:
Fatal: ASSERT: "first()" in file ...\MuseScore\libmscore\measure.cpp, line 1846
Clearly a fault in the build, is should get build in Release mode, which disables those crashes on failed assertions. Report this to the distribution maintainer and in the meantime use the AppImage
But see also #287263: MS file began crashing after every save (orchestra and parts) and https://musescore.org/en/node/287261
Workaround is to remove and re-generate the parts
In reply to Actually I found the problem… by Jojo-Schmitz
Thanks. I'm very grateful for your time in finding the fault. I deleted the parts and the problem was solved. My problem is that My mind is more "musical" than "technical" so, even though I'm getting better at it, a lot of the technical faults in software go over my head. Is there an advantage to using Appimage and, if there is, what is it?
In reply to Thanks. I'm very grateful… by phil_j
The advantage its is that it is supported here on musescore.org ;-)
And in this particular case that it won't crash on that score
In reply to The advantage its is that it… by Jojo-Schmitz
Thanks again. I've uninstalled the 'flatpak' version and I'm now using the appimage. It's performing well so far. It also seems a bit quicker on my 'starting to age' laptop. Could this be another advantage?
Anyway, I'm now going to repeat the same uninstall/install on my desktop. Thanks again again for your input. It's much appreciated
In reply to Thanks again. I've… by phil_j
Yes, possibly, a Debug build is probably slower than a Release build due to more debug output and possible less compiler optimization
In reply to Just to add, I am using… by phil_j
No crash while saving on Linux Mint 20.2 MS 3.6.2 AppImage
In reply to No crash while saving on… by Pentatonus
Hi, Thanks for your reply. All of the answers so far say that it doesn't crash on their machines so I'm a little puzzled. I'm going to try a previous suggestion and delete the parts. Will you play the file all the way through and tell me if it played OK. Thanks again.
In reply to Hi, Thanks for your reply… by phil_j
.