View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009271 | MMW v4 | Properties/Auto-Tools | public | 2012-04-16 01:34 | 2012-08-24 21:36 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | sometimes |
| Status | resolved | Resolution | suspended | ||
| Product Version | 4.0.3 | ||||
| Target Version | 4.1 | ||||
| Summary | 0009271: Heavy use of Auto-Tag From results in AV | ||||
| Description | User System Hardware: 4GB ram, x64, SSD system HDD http://support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-75044#arc MM.DB = ~710MB Lots of customization in both MM and OS, but I do not think that is main issue. System remarkably work fast and problem arise most often after several fast use of MusicIP tagger in combination to Amazon. Resources gets low ... This is only happening sometimes, it started to happen after hours of fast usage of Auto-Tag From Web. All Debug LOG files are uploaded to under "/MMeSupportTickets/EBH-762799 (Metadata Auto-Tag From Web Often Gives Access Violations)/" | ||||
| Additional Information | Ticket: EBH-762799 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Peke, could you please clarify, does MM memory usage increase after repeated usage of Auto-Tag From Web? Or maybe handles? Or could there be another reason? (Process Explorer is good for monitoring these variables) |
|
|
User uses x64 windows and have aprox 500Mb of free RAM available before MM start, which is normal downside of using x64 Win based on experience x86 will give aprox 1Gb Free RAM under same conditions. Memory and handles increase over time which is again normal due the fragmentation of RAM, which after hours of use result in swapping to HDD (even it is SSD) that slower response. Taking into account that MM is heavy multi threaded app, my best guess is that MusicIP tagger and heavy scripting add weigh. It is possibly that we have some memory leak which I can't replicate as all of my x64 have 8GB RAM. All indicate that Windows COM is failing due the lack of RAM and swapping. P.S. User indicated that he will test on another PC with more ram. |
|
|
Peke, I mean more rigorous testing, not just guessing. Take a look e.g. at 'Memory (Private Working Set)' column in Processes tab of Task Manager and try to find out whether you can reproduce some pattern in possible memory leaks. The same goes for Handles. |
|
|
I talked to user, it still occasionally happen and he was being able to note that components that eat up RAM are not part of MM but system files like firewall or IE ActiveX also it happen fairly sometimes (once in few days/weeks) |
