Interaction of multimeasure rests and Exclude from measure count

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

Jesu, Joy of Man's Desiring (short).pdf
The file above is a PDF of one part from the full score. A ZIP of the live file from which this part was extracted is included below. The problem arises in the first measure of this piece. It has been confirmed on both Windows and MacOS platforms.

In this piece, multimeasure rests are toggled on. With the first measure marked (in the Measure properties dialog) as Exclude from measure count the score appears as in the PDF, with a 1 above the initial rest and the measure count not excluding the first measure (note the count at the start of the second line). In other words, Exclude from measure count is marked but is not honored in this circumstance.

With the first measure not marked to be excluded from the measure count, the 1 above the first rest disappears. That does not seem necessary or proper behavior. Style settings say the 1 should be there.

If multimeasure rests are turned off for the piece then things work otherwise as expected.

While not specifically a part of this report, I can add that while working with this piece Musescore crashed twice. Once was specifically while working with the Exclude from measure count feature, when I first turned that setting on. The Diagnostics file and a ZIP of the dump files of that crash and the other one are included below. No crash has recurred subsequently so the cause is uncertain.

Supporting files, videos and screenshots

Jesu, Joy of Man's Desiring (short).zip

Musescore 4-7-3 diag.zip

Musescore crashed twice while working on this piece. The two dumps in the ZIP below are from those two crashes.

f7f7cfb3-0681-45c8-9ed3-619ed6c9f97a.zip

In which versions of MuseScore Studio is this issue present?

4.7.3 (others not tested)

Regression

I was unable to check

Operating system

Windows 11, macOS 26.5, probably others

Additional context

I was asked by Musescore support to report this issue here. They believe it is a genuine bug, heretofore unknown.

While working with this file I initially experienced also a failure to sync Exclude from measure count across the parts, but I have not been able to reproduce that. The crash occurred at about the same time as that failure and may have been induced by it.

I have not found a specific issue in Issue Tracker dealing with this issue. However, the first measure of this piece was a later addition to an existing score. That suggests a possible relationship to bug #32713.

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