musescore / musescore/MuseScore

MuseScore 4.7.3 on M1 MacBook crashes quite frequently and I find no crash report or log entry

Open
#33,950 12 comments 0 reactions 3 assignees View on GitHub

@zacjansheski is already working on this.

Since Jun 25, 2026.

awaiting reply from user crash needs review
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Crash or freeze

Description with steps to reproduce

Installed
OS: macOS Tahoe (26.5.1),
Arch.: arm64,
MuseScore Studio version (64-bit): 4.7.3-260608135,
revision: github-musescore-musescore-cf9860c

Unfortunately so far I haven't found any clues about how to reproduce these and, as mentioned, I don't find any crash reports or anything useful in the log.

I'll try to keep better track from now on and try some specific steps.

Is it possible, perhaps, to activate some kind of more verbose logging that might help shed some light on the cause?

Supporting files, videos and screenshots

(As mentioned, I haven't found any crash reports yet nor methods to reproduce. I'll include a few lines from the bottom of my log so this field is not empty

2026-06-25T11:38:51.888 | INFO | main_thread | NotationProject::doSave | success save file: "/Users/tbh/Library/CloudStorage/Dropbox/music/MuseScore/ScoresMS4/TryArranging/See_my_friends_SATB_MS4.mscz"
2026-06-25T11:39:35.263 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: rewind
2026-06-25T11:39:35.964 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: play
tbh@MacBook-Pro ~ % tail -f ~/Library/Application\ Support/MuseScore/MuseScore4/logs/MuseScore_260625_113651.log
2026-06-25T11:38:43.847 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: pad-note-8
2026-06-25T11:38:47.189 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: pad-note-4
2026-06-25T11:38:47.790 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: note-f
2026-06-25T11:38:48.444 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: notation-move-left
2026-06-25T11:38:48.687 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: notation-move-left
2026-06-25T11:38:49.856 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: tie
2026-06-25T11:38:51.689 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: file-save
2026-06-25T11:38:51.888 | INFO | main_thread | NotationProject::doSave | success save file: "/Users/tbh/Library/CloudStorage/Dropbox/music/MuseScore/ScoresMS4/TryArranging/See_my_friends_SATB_MS4.mscz"
2026-06-25T11:39:35.263 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: rewind
2026-06-25T11:39:35.964 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: play
)

In which versions of MuseScore Studio is this issue present?

MuseScore Studio version (64-bit): 4.7.3-260608135,

Regression

I was unable to check

Operating system

macOS Tahoe (26.5.1)

Additional context

No response

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.