Memory leak with MuseSounds/MuseSampler

[DmitryArefiev]

Steps to reproduce

1. Open Task Manager (and watch MuseScore)
2. Open big score with MuseSounds (MS4SOUNDS_Beethoven__Symphony_No._9__Op._125.zip)
3. Playback, stop playback/start playback, start playback from beginning etc.
4. Observe RAM amount (it's growing)
5. Close score - RAM is not released as it should
6. Open score again - it takes more RAM than before

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

[metasekk]

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).