MuseScore
MuseScore crashes when I try to open parts from within a score. I can get as highlighting which part I want to open in the "Parts" dialogue; when I click "open selected" the program crashes. This is new behavior and affects other scores I've tried to reproduce the behavior. The only new software on my system since the behavior began is the update of MuseScore. The score itself opens and saves just fine.
I am using MuseScore Studio 4.3.0.241231433 on a Mac Mini, OS 13.3.
I've attached the crashing file that has the part I'm trying to open, and pasted in the summary of the crash report, in case it's handy. The entire report is too long to include without somebody requesting.
Translated Report (Full Report Below)
Process: mscore [15180]
Path: /Applications/MuseScore 4.app/Contents/MacOS/mscore
Identifier: org.musescore.MuseScore
Version: 4.3.0 (241231433)
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2024-05-13 13:16:25.5770 -0400
OS Version: macOS 13.3 (22E252)
Report Version: 12
Anonymous UUID: 358585A6-E551-895C-0BF6-A9855C0C80D2
Time Awake Since Boot: 3600 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000040
Exception Codes: 0x0000000000000001, 0x0000000000000040
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [15180]
VM Region Info: 0x40 is not in any region. Bytes before following region: 140723000360896
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
mapped file 7ffca072c000-7ffcaebd8000 [228.7M] r-x/r-x SM=COW ...t_id=408d3551
| Attachment | Size |
|---|---|
| BWV 527 Bc.mscz | 87.63 KB |
Comments
Most likely related to this issue: https://github.com/musescore/MuseScore/issues/22759 (fixed for the next 4.3.1)
Meanwhile, you can create/open parts:
Or
EDIT: After further checking, it is possible to confirm that this is the issue, and that the patch has just been merged into the code (verifiable in a Nightly or while waiting for 4.3.1 to be released).
In reply to Most likely this issue:… by cadiz1
Hi Cádiz. Thank you for the info. I don't understand the discussion on the technical link, but I do understand your explanation on workarounds! And your research into the code revisions would seem to indicate that once I am able to upgrade to the newest release, this problem will go away. Many thanks, once again. —Richard
In reply to Hi Cádiz. Thank you for the… by RickyChitarrone
"once I am able to upgrade to the newest release, this problem will go away"
That's right.