musescore / musescore/MuseScore

Crash when moving dock panels (palettes, properties, mixer, etc.) onto second screen

Open
#12,939 3 comments 0 reactions 4 assignees View on GitHub

@mathesoncalum is already working on this.

Since Nov 11, 2025.

crash Fixable in dock system update os: windows P1
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Describe the bug
CTD when moving 'palette', 'instruments', & 'properties' panels onto a second monitor. (Plus note input toolbar issue with second screen)

To Reproduce
Steps to reproduce the behavior:

  1. Click on 'palette' header and drag to second screen
  2. CTD

Expected behavior
Panels to be draggable to second screen.

Screenshots

https://user-images.githubusercontent.com/92125704/185716230-ffc5fa36-b3ef-49b0-8824-4c1507a58ad3.mp4

Platform information

  • OS: Windows

Additional context
On one occasion I first undocked the panel on the main screen before moving it onto the second screen; this worked and did not result in a CTD (panel scaling was slightly off, though). I tried to record this behavior and now only experience a CTD:

https://user-images.githubusercontent.com/92125704/185716421-7ea55190-b43f-4729-85da-8e2fb3cee8d5.mp4

Moving the note input toolbar does not result in a CTD, but the toolbar does not function (it was draggable post move in the recording, but this doesn't always happen) and the scaling is off (related to #9505?). When restarting Musescore, the toolbar appears on the second screen scaled correctly and fully functional.

https://user-images.githubusercontent.com/92125704/185716971-be362d64-27df-4802-a3f5-1bfce079fcbf.mp4

Undocking the panel on the main screen and then moving it across did work at first, but now results in the same behavior:

https://user-images.githubusercontent.com/92125704/185717205-a0ad7404-601f-4a33-89b0-9833cae6748f.mp4

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.