musescore / musescore/MuseScore
Articulation assigned to barline causes application crash
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Crash or freeze
Bug description
In MS 4.1.1 you can attach an articulation (like staccato) to a barline. This does not cause an issue.
However, when this score is then opened in MS 4.2, the application crashes when it needs to display the measure which contains this element.
In MS 4.2, when you select a barline and then click on the palet icon staccato, the application crashes immediate.
Steps to reproduce
In MS 4.2:
- Create a new score and add at least 1 instrument
- Select a barline
- Click the staccato accent in the articulations palet
In MS 4.1.1:
Perform the same actions as describe for MS 4.2 and save the file. No issues.
Now open the saved file in MS 4.2. App crashes on load.
Screenshots/Screen recordings
Attached mscz file is created in MS 4.1.1. When this is open in MS 4.2, the app crashes.
NOTE: Remove the .zip from the filename, this was only added to allow adding the file to the github issue.
MuseScore Version
4.2.0
Regression
Yes, this used to work in a previous version of MuseScore 4.x
Operating system
Windows 11
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the crash in MuseScore 4.2 using the attached .mscz file and the listed steps, then compare the same operation in 4.1.1. Trace how an articulation assigned to a barline is handled when the measure is displayed or loaded; done means the score opens and the articulation action no longer crashes the application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100