musescore / musescore/MuseScore
Memory leak with MuseSounds/MuseSampler after closing score
Open
Nobody has claimed this yet.
P2
regression MS4
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Other type of issue
Description with steps to reproduce
Results on Win (similar on Mac), latest 4.4 master and musesampler 0.100.0.299:
- Measure memory - 177Mb
- Open MS4SOUNDS_Beethoven__Symphony_No._9__Op._125.zip and close it (after loading samples)
- Measure memory - 686Mb
- Open and close the same score
- Measure memory - 929Mb
- Open and close the same score
- Measure memory - 1047Mb
- Open and close the same score
- Measure memory - 1217Mb
- Open and close the same score
- Measure memory - 1309Mb
Memory leak after step 4 doesn't occur with MS Basic
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/7cfd4e14-60ed-4b08-ba0a-1b00df4dcd50
What is the latest version of MuseScore Studio where this issue is present?
4.4 master
Regression
Doesn't occur in 4.2.1 (with the same musesampler version). Checked only on Windows
Operating system
Windows 10, Mac 13.6
Additional context
Similar to #23112 but without so memory loss
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
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.
Assessment
This issue has not been assessed yet.