View Issue Details

IDProjectCategoryView StatusLast Update
0001730MMW v4Properties/Auto-Toolspublic2005-01-16 01:30
Reporterrusty Assigned To 
PriorityimmediateSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Fixed in Version2.3 
Summary0001730: Auto-Tag from Amazon: Memory Leak
DescriptionTested build 830.

When auto-tagging tracks, memory utilization keeps going higher and higher. As memory utilization increases (beyond 100,000K), other behaviours start occuring:
-Access violations when clicking OK on the properties panel
-Impossible to close MediaMonkey due to 'Background threads'
-When MediaMonkey does close and then restart, it starts up with a completely empty Library (with alll nodes in the library not even appearing). Note: this occurs because the original instance of MediaMonkey never actually closed.
TagsNo tags attached.
Fixed in build831

Activities

jiri

2005-01-07 07:52

administrator   ~0005135

Fixed in build 831.
 - I found and fixed several memory leaks. I'm not sure if they could have caused so much memory utilization, but probably yes.

rusty

2005-01-07 17:09

administrator   ~0005138

Tested in 831: I'm still finding that when I Auto-tag albums, memory utilization continually increases (~500k per tagged album).

rusty

2005-01-12 13:04

administrator   ~0005152

I can't seem to trigger the instability that I'd observed. I will continue to keep an eye out for the problem, but for now, I'm not sure what actually triggers the problem.

rusty

2005-01-16 01:30

administrator   ~0005170

Closing, cannot replicate problem.