musescore / musescore/MuseScore

Crash caused by arrow scrolling notes that have the Swell Gamba 16' soundflag in the Union Chapel Organ (MuseSounds)

Open
#34,196 0 comments 0 reactions 3 assignees View on GitHub

Nobody has claimed this yet.

MuseSounds needs review P1 regression MS4
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

VST bug

Description with steps to reproduce

Load any instrument and apply the Union Chapel Organ MuseSounds VST as the soundfont.
Using CTRL + T to open the sound flag menu, apply the (Swell) Contra Gamba 16' option.

Musescore will now crash when you use the arrows to navigate notes on the instrument in the section where the (Swell) Contra Gamba 16' sound flag is enabled.
Musescore is not meant to crash when you use the arrows to navigate notes in this way.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/95556863-a884-4dee-8638-d65629299e93

gambacrash_diagnostics.zip

nightlylatestGambacrash_diagnostics.zip

In which versions of MuseScore Studio is this issue present?

(64-bit) 4.7.4 and latest nightly build 4.74-260714045, revision github-musescore-musescore-4c3a13c

Regression

I was unable to check

Operating system

OS: Windows 11 Version 25H2 or later, Arch.: x86_64

Additional context

Works on MuseScore Studio version (64-bit): 4.7.4-260706075, revision: github-musescore-musescore-7688c00
Also works on latest nightly: MuseScore Studio version (64-bit): 4.7.4-260714045, revision: github-musescore-musescore-4c3a13c
(The amount of times I use the arrow key before it crashes seems to be random, or it could be something to do with CPU or memory; I can sometimes scroll numerous times before the crash, but in some instances, I scroll once and it crashes.)

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.