musescore / musescore/MuseScore

Crashes with partial lyrics lines hyphens

Open
#32,927 0 comments 0 reactions 1 assignee View on GitHub

@miiizen is already working on this.

Since Apr 7, 2026.

  • #32947 by @miiizen — merged
crash P1 regression MS4
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

The order of creating repeats/notes appears to influence how this presents.

CASE 1:

  1. Add a note at the start of a bar (e.g. bar 3 in a new score).
  2. Create 1st and 2nd endings with the appropriate repeat barline (see video below).
  3. Add a partial lyrics line hyphen to the note. NOTICE here that the 2nd ending vanishes.
  4. Select the hyphen.
    MSS usually crashes here. Else, continue with step 5.
  5. Change the Set to verse property from 1 to 2.
    RESULT: CRASH

CASE 2:

  1. Create 1st and 2nd endings with the appropriate repeat barline.
  2. Add a note at the start of the 2nd ending.
  3. Add a partial lyrics line hyphen to the note. NOTICE here that the note vanishes.
  4. Select and deselect the hyphen (seems to be a necessary step to reliably reproduce the crash).
  5. Close the score.
    RESULT: CRASH
Supporting files, videos and screenshots

Case 1:

https://github.com/user-attachments/assets/2f756d69-88c7-4e70-961b-33a9e0a7ee00


Case 2:

https://github.com/user-attachments/assets/af808316-318d-4c18-82a5-9b6cb0a534f3

In which versions of MuseScore Studio is this issue present?

Latest nightlies

Regression

Yes. Did not crash in 4.5.2. Partially reproducible in 4.6.0 - 4.6.5.

Operating system

Ubuntu 24.04.4 LTS

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.