musescore / musescore/MuseScore

Crash when the beat the initial tempo marking is anchored to is deleted and then pasted on

Open
#28,172 0 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

crash P1
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

If the score has a tempo marking at the beginning, and you then remove the first beat of that measure, which then shortens that measure, MuseScore will crash if you attempt to paste something onto that first measure. If this sounds complicated, I have attached an example score with steps where you can try it yourself.

  1. In the New Score wizard, include a tempo marking, or after the score is created add a tempo marking to the first beat.
  2. Add a rest to the first measure, for example by selecting the measure rest and pressing 5.
  3. Delete that first rest by selecting it and pressing Command Backspace, shortening the measure.
  4. Try to paste something onto the first (now shorter) measure. MuseScore crashes.
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/856a0115-0449-4d6e-a7ae-d4e41d2e88f1

Paste Crash.mscz.zip

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

4.5.2

Regression

No (same crash in MS3.6.2)

Operating system

macOS 13.7.2 (Windows and Linux too)

Additional context

I have tested on MuseScore 3.6.2 and the issue was present there as well. It is not reproducible in MuseScore 2 because MuseScore 2 did not support shortening measures by deleting notes or rests.

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.