View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003858 | MMW v4 | Other | public | 2007-10-29 21:12 | 2007-11-01 19:23 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.0 | ||||
| Summary | 0003858: Memory utilization is very high | ||||
| Description | MM3 memory utilization for equivalent sized libraries: MM3 47MB Winamp 17MB WMP 30MB Hopefully this is related to the debug version of the app, but we need to examine this before RC-2. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1099 | ||||
|
|
My experiences: 1. If I start MM it takes 30 - 40 MB of memory, but if I minimize it to task bar and then retore it takes only 10 - 12 MB !! Important note: minimization significant decreases the memory only if I minimize to Task Bar, in case of minimizing to tray/MicroPlayer it doesn't seem to decrease memory at all. 2. On the other hand if I browse my collection using AA view it is able to grow up to 80 MB! After switching back to details view it still takes 80 MB! |
|
|
fyi, my experience is pretty much the same as Ludeks, but maybe a little less consistent. 1) a) Starting MM: 0000010:0000045 MB b) Minimize to taskbar --> ~7MB c) Maximize back to details view --> 14 MB (in NP node) d) Switch to other nodes --> 25 MB (why so much less than 1a??) 2) a) Switching to AA view and scrolling through the art --> 120MB b) Minimize to taskbar --> ~6MB c) Maximize back to AA and scrolling through the art --> 60MB (why only half of 2a??) Note: like ludek: minimizing to MiniPlayer or MicroPlayer didn't clear memory in the same way as minimizing to the taskbar. |
|
|
Testing note: Mem Usage from Task Manager isn't the best indicator of memory used by application - it's rather about memory currently taken, not about all bytes allocated. Upon Minimization Windows automatically releases memory, but application still has pretty much the same memory utilization! Much better means of measuring memory utilization is Process Explorer tool, Private Bytes column better shows memory taken by given process. Based on this, my current measurements show that MM (release version without debug info) takes similar amounts of memory as WinAmp, WMP seems to do some tricks, Private Bytes is often like 20MB, while Working Set is usually higher. Anyway, I'm still reviewing the subject... |
|
|
So far I have at least fixed a couple of small memory leaks. |
|
|
Fixed few leaks in some parts of code (auto-organize, filters, AA view). |
|
|
I'm resolving this for now. In the release version, MM doesn't seem to be significantly more hungry than other applications or MM 2.5. We can try to even more improve this in the next version. |
