Memory leaks And UI No Response

• Jul 2, 2019 - 05:56
Reported version
3.2
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

After upgrading to musescore 3.1, there is a problem of increasing memory when selecting Musical Instruments, and the interface is not responsive. Memory leaks reach 2GB and keep growing , The problem of musescore 3.2.2 still exists when tested
No such problem was found with musescore 2.3.2， I used Windows 10 64bit Version 1903

I tried to test it on another computer and occasionally had similar problems

Attachment Size
MemoryLeaks.png 7.12 KB
NoResponse.png 27.18 KB

Comments

• Jul 2, 2019 - 08:13
Frequency Many ⇒ Once
Severity S1 - Blocker ⇒ S3 - Major
Status active ⇒ needs info
Type Ergonomical (UX) ⇒ Functional

What do you mean by when selecting Musical Instruments ?

Reply

• Jul 2, 2019 - 09:00

This is what I did, and don't see any (significant) memory increase.
Starting MuseScore with last session, which opens a score of mine, and I see memory starting at some 150MB, waiting till sound works (i.e. until the default soundfont is loaded, in background), raises memory to some 346MB.
Pressing I adds another MB, adding a few instruments, closing the dialog and I'm at 351MB
Nothing dramatic as far as I can see, and of course a score with more instuments needs more RAM

Reply

• Jul 2, 2019 - 13:02

After repeated testing and verification， I have not encountered this problem since I tried to shut down the translation software, which may be the cause of some incompatibilities between the translation software and Qt， I'll continue to see if the problem recurs
Attached is a GIF file with screen manipulation
Thank you for your attention

Attachment Size
shortcut_I.gif 798.59 KB

Reply