MuseScore 3 crashes on every attempt to save

• Feb 11, 2019 - 04:21

I have seen the other reports from 2016 -2019, but no solution.
Luckily I still have version 2, because MuseScore 3 crashes every time I try to save a file (Windows 10 64 bit)
I will attach one, but it happens to all files

Attachment Size
Mood_Indigo.mscz 28.38 KB

Comments

• Feb 11, 2019 - 07:19

I cannot reproduce here. I open your file, edit two-three things (pitch of a few notes), and all is normal when saving.
Here first saving: 1Mood_Indigo.mscz
And a second saving (sorry for the wrong notes): 2Mood_Indigo.mscz
Are you doing other specific things before saving?

And first please, try to do: menu "Help" -> click "RevertToFactorySettings"

Reply

• Apr 15, 2019 - 04:37

Hi,Thanks for your reply. Sorry it's been 2 months, but I have been busy! I used MuseScore 2 when possible due to this problem. I restored to factory settings and the problem persists. Whenever I make anything on MuseScore 3, whether it's a download from musescore.org, or some simple music for students, as soon as I try to save or export, it crashes/closes. Then when I reopen, it says "musescore closed unexpectedly. Would you like to restore the session?" But it doesn't help because my work is lost and the problem remains...I can not make new work on MuseScore and save it. And now MuseScore 2 is no longer practical because everything on MuseScore.org is geared towards 3. I can't even do the work on 3 and paste it into 2. Do you think 3 crashes because 2 is still on my computer?

Reply

• Apr 15, 2019 - 04:57

So what happens, exactly, if you go to File / Save As? Do you get the dialog prompting you to select a folder and filename? What folder are you choosing? Anything unusual about it - on a network, removable drive, ...?

Reply

• Apr 25, 2019 - 14:10

Thank you for your suggestion. Due to another reply I did a "search for updates" and it did indeed install an updated version, then I opened it "run as administrator," but the same problem happens. If I try "Save as," Save selection," or "export," anything that open a dialogue box, the mouse arrow circles/cycles for a 3-5 seconds, then the software closes.

Reply

• Apr 25, 2019 - 14:11

Thank you for your questions. Due to other replies I did a "search for updates" and it did indeed install an updated version but the problem persists, then I opened it "run as administrator," but the same problem happens. If I try "Save as," Save selection," or "export," anything that open a dialogue box, the mouse arrow circles/cycles for maybe 2-3 seconds, then the software closes.

Reply

• Apr 25, 2019 - 14:08

Thank you for asking. Your question caused me to do a "search for updates" and it did indeed install an updated version, but the same problem happens. If I try "Save as," Save selection," or "export," anything that open a dialogue box, the mouse arrow circles/cycles for a 3-5 seconds, then the software closes.

Reply

• Apr 25, 2019 - 16:47

Hi thanks. I checked the link and there are no known relevant incompatibilities. I reverted to factory settings again. Still shuts down on any save attempt, a couple of seconds after a dialogue box opens. Would you suggest I rip and reinstall? That's the only thing I can think to do next.

Reply

• May 20, 2019 - 03:28

HI again,
My other work is winding down for the summer and I'm getting back to this, as I hope to use MuseScore a lot this summer. Regular "save" crashes, just the same as any operation I try that opens any dialogue box. I sent the crash report.
I sure hope we have a breakthrough and wind up solving this mystery!
This happens with "save" and "save as." It happens if I try altering something I made previously or downloaded so that it is trying to save the alterationc to the "downloads" folder. It happens if it is something I tried altering and try saving to any other folder a few windows deep. It happens if I create a new score and allow it to choose a default folder which in my computer is "Documents - MuseScore3 - Scores." The same is true with the "export" command as well.
MuseScore 2 continues to work beautifully, but as you probably know, none of the music from musescore.org is compatible with 2, so it is not as useful to me as the more current version would be if it didn't crash upon any attempt to save.

Reply

• May 20, 2019 - 07:23

Thank you all so much! I'm glad I'm not the only one having trouble.

Another user suggested double-clicking on a mscz file and from Preferences disable Show start center, but I tried this and it didn't work for me. I do appreciate the suggestion.

I'm back to v2 until they come up with some fix.

Reply

• Aug 24, 2019 - 02:11

I have this issue too! I'm on a Mac. Here's a TINY part of my crashlog:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000000f0
Exception Note: EXC_CORPSE_NOTIFY

Does that mean anything to someone?

Reply

• Aug 24, 2019 - 12:51

Right now my best guess is the score (or perhaps one of its parts) is corrupt.

FWIW, there is one recently-fixed bug that can cause corrupt parts and seems to have affected a lot of people: #290546: Copy-paste a part with mm rests on another part/mm rests leads to corruption/crash. Even though the bug is fixed in 3.2.3, older scores that were already corrupted may still be a problem. Although it's not feasible to implement special workarounds for each corruption (inevitably a corrupt score is likely to lead to a crash), this particular one seems like it might be worth the effort.

Reply

• Aug 27, 2019 - 01:15

If it crashes the program don't do it...Just kidding.

Can you attach the score where you are trying to edit the time signature and tell us what you are doing so we can recreate the crash? Someone can then find the cause and probably a workaround that will allow you to continue.

Reply

• Sep 6, 2019 - 12:21

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.2.3.7635, revision: d2d863f

Having this same problem, but it doesn't seem to be an issue with the saving, but something in the routine that opens the save as/open dialog. I have autosave turned on and I'm not crashing every 2 minutes and I can ctrl+S all day long as long as the dialog doesn't have to open. This has lead me to create some "template" files that a copy before starting a new piece to avoid the initial save dialog. The problem is only when the dialog has to open. It doesn't have to be a specific score. I can create a brand new score, save and crash. I can have no scores open, and Ctrl O and it crashes. The dialog will render and then boom.

If it helps, here's the output of a Event Log:

Faulting application name: MuseScore3.exe, version: 0.0.0.0, time stamp: 0x5d22fc07
Faulting module name: ntdll.dll, version: 10.0.17134.799, time stamp: 0x7f828745
Exception code: 0xc0000374
Fault offset: 0x00000000000f479b
Faulting process id: 0x7eb0
Faulting application start time: 0x01d564a15ccbd8ac
Faulting application path: C:\Program Files\MuseScore 3\bin\MuseScore3.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: bd82496e-49ee-4747-aeae-cda03687ae4d
Faulting package full name:
Faulting package-relative application ID:

Reply

• Sep 6, 2019 - 14:36

Well, if the crash happens on opening the file dialog, it's not very likely connected to the score. At least, not the currently open score. More likely, there is some other score in the same folder that for whatever reason is causing a problem, like there are invalid characters in the filename or something.

Reply

• Sep 6, 2019 - 15:24

I'm inclined to agree Marc. The problem here seems a bit more fundamental to the OS behavior rather than any score itself. And this is every time that little file system explorer window opens, anywhere in the application, not just saving and opening scores.

Did another factory reset for giggles. Showed hidden files and cleaned out my scores directory and it still happens. I've tried running the program in different OS compatibility modes with no success. I'd just give up and use Musescore 2, except I'm too stubborn to let this problem lie.

Reply

• Sep 6, 2019 - 17:20

Glad I remembered that, and that it worked!

Still would be good to understand what was happening. My best guess is, some other application on your system creating some sort of DLL conflict that only got hit when using native dialogs. Doesn't seem to be what anyone is seeing (of all the problems with save reported, I don't recally any happening on open, or being connected to dialogs).

Reply

• Dec 29, 2019 - 11:09

Linux (Mint 19.3 Cinnamon) MuseScore3 3.3.4 appimage crashes on save or save as. Running MuseScore -w provides the following:

/usr/lib/x86_64-linux-gnu/libjack.so.0
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
/tmp/.mount_MuseScnSulkn/AppRun: line 48:  3130 Aborted                 (core dumped) "${APPDIR}/bin/mscore-portable" "$@"

Does any body have a clue about this?

Reply

• Dec 29, 2019 - 11:42

See https://musescore.org/en/node/81411 ? Quite old, but might give some hint?

Not sure what the -w option is supposed to buy in this context (it just disables web access, very unlikely to cause issues on save), try -d (for debug, more output), -s (no sound, not likely involved with crashes on save though) or -F (revert to factory settings)

If it is happening on a particular score, please share it here

Reply

• Jun 21, 2020 - 20:25

I bumped into this issue too. Same error message as reported in the discussion here.
It is the file that has gotten corrupted.

I managed to "Save" it, by doing this:
1. Open the file
2. Select everything (Ctrl+A)
3. In File menu, choose Save Selection -- and save as a new file.

I also deleted the .temp file corresponding to the corrupt score. Inconclusive on the effect of that.

Reply

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