-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leak with MuseSounds/MuseSampler #23112
Comments
FYI, the second part of this issue, whereby closing and reopening a score doesn't free up memory when using MuseSounds, has had its own report here: #22721 A point that could be worth mentioning about the second part of the issue (that is, #22721): I can reproduce it in 4.2.1 (as well as in olders versions actually), whatever MuseSampler version I'm using. However, the rate of growth of memory is much lower than in 4.4 or 4.3, which can give the impression that it doesn't happen (and in that, it is similar to the scores using MS Basic instead of MuseSounds, that do also exhibit memory increase at lower rates). |
Because it locks the pointer, EventAudioSource loses ownership of it and can no longer destroy it
Because it locks the pointer, EventAudioSource loses ownership of it and can no longer destroy it
Because it locks the pointer, EventAudioSource loses ownership of it and can no longer destroy it
Steps to reproduce
Screenshots/Screen recordings
bandicam.2024-06-06.15-29-35-181.mp4
MuseScore Version
4.4
MuseSampler 0.6.3 (latest version from MuseHub)
Regression
Doesn't occur in 4.2.1 (with the same musesampler version)
Operating system
Windows10
Additional context
No response
The text was updated successfully, but these errors were encountered: