This was on a Mac running MacOs 10.14.3 Mohave and it was MuseScore 3.0.2.20666 revision 8ca4d2c. It was suggested I revert to factory settings and this also resulted in a crash.
Myself I'm using the AppImage of Linux, there I can't reproduce this crash. Maybe someone other with a Mac. Is it possible to start MuseScore from a command line with Mac and if, is there any output? Could you check if it works by using a command line option, such as -s or other (https://musescore.org/en/handbook/3/command-line-options)?
i have the same problem. iMac with MacOS 10.14.4, and Musescore 3. crashes every time i quit. complete error log is attached. hope someone is looking into this? thanks! ... karl
Comments
Some more information (operating system, revision of MuseScore/MuseScore version)?
Did you check if revert to factory settings solves the problem?
This was on a Mac running MacOs 10.14.3 Mohave and it was MuseScore 3.0.2.20666 revision 8ca4d2c. It was suggested I revert to factory settings and this also resulted in a crash.
Myself I'm using the AppImage of Linux, there I can't reproduce this crash. Maybe someone other with a Mac. Is it possible to start MuseScore from a command line with Mac and if, is there any output? Could you check if it works by using a command line option, such as -s or other (https://musescore.org/en/handbook/3/command-line-options)?
In reply to Myself I'm using the… by kuwitt
Same here, but if I disconnected the Novation Launchkey the problem would be gone.
Same here. Running macOS 10.13.6 "High Sierra" on a 2017 iMac. The two last recent updates always crash on exit...
Same problem, Mac OS 10.13.6, newest Musescore (downloaded today)
Duplicate, see https://musescore.org/en/node/281867
or #281867: "MuseScore quit unexpectedly" when closing MuseScore 3.0.[1-5] on macOS with a MIDI device
In reply to Some more information … by kuwitt
i have the same problem. iMac with MacOS 10.14.4, and Musescore 3. crashes every time i quit. complete error log is attached. hope someone is looking into this? thanks! ... karl
It is still a duplicate and is being looked after in the other issue, and as you may see there it is even fixed, for the upcomming 3.1