View Issue Details

Jump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0022220MMW 5Generalpublic2026-07-10 02:292026-08-13 18:27
Reporterlowlander Assigned To 
PriorityimmediateSeveritycrashReproducibilityalways
Status resolvedResolutionfixed 
Product Version2027 
Target Version2027Fixed in Version2027 
Summary0022220: Add/Rescan Files Memory Leak
DescriptionAdd/Rescan Files will keep increasing memory usage during scanning. At 13000 files scanned memory usage was over 2GB. Eventually MediaMonkey will crash.
Steps To Reproduce1 Disable Only for files with changed timestamp or size
2 Start Add/Rescan Files
--> White screen after scanning files for a while
Additional InformationTicket 18202
TagsNo tags attached.
Fixed in build3517

Relationships

related to 0022185 closedmichal Opening Properties on multiple files causes high memory usage/slow to use 
related to 0022266 resolvedLudek Mapped drive to UNC do not correct tracks in Library during rescan 
related to 0022221 closedmichal DB/Tag Mismatches Memory Leak 

Activities

michal

2026-07-23 12:20

developer   ~0081657

Significantly improved in build 3515. The main cause of the quick increase is fixed. There is still some minor RAM usage increase during every scan, but not so serious, resolving, so the main problem can be tested. I added better diagnostics of RAM handling, so we could analyze mem leaks better from debug logs.

lowlander

2026-07-30 19:40

developer   ~0081770

This one still happens on 3516. Sitting at 1800MB memory use after scanning 30,000 files. Note that this is a forced rescan (as I need to get Synced Lyrics read from files) of all files.

michal

2026-08-13 18:27

developer   ~0081836

I did several related fixes to 3517, some could improve speed and RAM usage significantly, especially with large Playing list present, I hope it will be better.