In master on Windows, memory usage increases linearly over time for both MS Basic and Muse Sounds, at different rates

[metasekk]

Issue type

General playback bug

Bug description

Closing and reopening a score leads to a gradual (affine) increase in the RAM memory used by MuseScore, with very rapid growth for Muse Sounds, as though the sound banks loaded in memory were never released, but instead, stacked.

Steps to reproduce

1. For Windows users, open the task manager.
2. Open this score for Muse Sounds (empty score with Muse Sounds as the default profile) or this one for MS Basic (same score with MS Basic as the default profile).
3. Close it and reopen it several times, and compare the memory of the task "MuseScore4.exe" after each cycle.

I provide a (tedious) video here, demonstrating this process step by step (beware: I couldn't change the language of the task manager, therefore it is in French; memory is the column entitled "Mémoire" - a quite transparent one). The results are rendered quantitative below.

Screenshots/Screen recordings

I conducted two studies of repeated closing/reopening cycles (three times each), for MS Basic and MuseSounds respectively. Here are my findings:

For Muse Sounds :

• The figures are highly reproducible : the standard deviation for each figure is <5 Mo.
• It increases monotonically : no drop nor jump occured in the three cases.

For MS Basic :

• The figures are also highly reproducible on my side : the maximum standard deviation for each figure is <20 Mo.
• A very surprising "jump" from ~350 Mo to ~800 Mo can be seen for MS Basic. It was observed in the three studies, and every time between 5 and 10 re-opening cycles. In 1 case (over 3), there was another drop between 15-20 reopenings, where the memory went back to ~400 Mo.

I don't know what it reveals about the way the memory allocation/deallocation is implemented, but based on this, I suspect it is different between MS Basic and Muse Sounds, which was quite surprising to me. For MS Basic, the jumps and drops in memory might indicate something dubious in the handling of it.

MuseScore Version

Latest 4.4 master (tested on MuseScoreNightly-241290306-master-48c7fdd-x86_64)

Regression

I don't know

Operating system

Win10 (22H2); RAM: 16Go; CPU: Intel Core i5-9300H (2.40GHz)

Additional context

I could only conduct this experiment on Windows 10.

Somewhat related to #22094 and possibly #22710.