View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001730 | MMW v4 | Properties/Auto-Tools | public | 2005-01-07 03:24 | 2005-01-16 01:30 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Fixed in Version | 2.3 | ||||
| Summary | 0001730: Auto-Tag from Amazon: Memory Leak | ||||
| Description | Tested 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. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 831 | ||||
|
|
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. |
|
|
Tested in 831: I'm still finding that when I Auto-tag albums, memory utilization continually increases (~500k per tagged album). |
|
|
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. |
|
|
Closing, cannot replicate problem. |
