musescore / musescore/MuseScore

MS4.4 crashes if mixer undocked and the user double clicks the Mixer button 2 or more times

Open
#24,243 13 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

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
  1. Start or Restart MuseScore 4.4
  2. New score / Done
  3. undock mixer
  4. double click the mixer button
  5. double click again

Result: MuseScore usually crashes. IF not, double click another time or two.

NOTE: I was able to replicate this a dozen times in a row. Then I couldn't replicate. So after reopening MS4.4 I dragged the mixer a short distance, double-clicked the Mixer button, and again incurred the crash.

UPDATE: New alternate replication steps:

Today the crash occurred after 4 single clicks to the Mixer button

  1. Start or Restart MuseScore 4.4
  2. New score / Done
  3. undock Mixer or move the Mixer
  4. single click the mixer button 4 times
Supporting files, videos and screenshots

It's always a silent crash, so there's no diagnostic log.

What is the latest version of MuseScore Studio where this issue is present?

OS: macOS 13.5, Arch.: arm64, MuseScore Studio version (64-bit): 4.4.0-242390800, revision: github-musescore-musescore-0fcd11b

Regression

No.

Operating system

Mac OS 13.5.2

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.