View Issue Details

IDProjectCategoryView StatusLast Update
0011203MMW v4Synchronizationpublic2013-08-29 21:51
ReporterLudek Assigned To 
PriorityurgentSeverityminorReproducibilityunable to reproduce
Status closedResolutionfixed 
Product Version4.1 
Target Version4.1Fixed in Version4.1 
Summary0011203: MM 4.1 uses 50% CPU every 30 seconds for some users
DescriptionAs reported here:
http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=73487

MM 4.1 uses 50% CPU every 30 seconds for some users, this is related to fix of 0009977 , because it is d_WMDM.dll that eats the resources.
TagsNo tags attached.
Fixed in build1656

Relationships

related to 0011587 closedLudek Android device can't be browsed if it's unlocked while connected 
child of 0009977 closedLudek Certain android devices aren't recognized over MTP but are by WMP 

Activities

Ludek

2013-08-26 21:31

developer   ~0037281

Last edited: 2013-08-26 22:36

Based on the log attached to the forum post:
The performance issue is caused when calling IWMDMEnumDevice::Next method ( http://msdn.microsoft.com/en-us/library/windows/desktop/ff801491(v=vs.85).aspx ) when it takes 3 seconds for each drive (H:, K:, J:, I:, L:) to enumerate it with error code ERROR_NOT_READY (0x15) - The device is not ready

Solution seems to be to either:
a) revert the perodical check from 0009977
b) re-call the device enumeration less often or (instead of periodically every 30 sec.) call it after 30 seconds, then after 1 minute, then 2 minutes, then 4 minutes and so on.

Ludek

2013-08-26 22:28

developer   ~0037282

Last edited: 2013-08-26 22:53

Fixed in build 1655 using solution b), but I am not sure about the solution, reverting 0009977 should be taken into account.

Ludek

2013-08-28 10:17

developer   ~0037319

Last edited: 2013-08-28 10:24

Fixed in build 1656 using solution a) - i.e. the periodic check from 0009977 was reverted, workaround is to restart MMW to re-run device enumeration

peke

2013-08-29 21:51

developer   ~0037382

Verified 1656 It doesn't happen anymore on My LG after update to JB 4.1.2