View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0018288||MediaMonkey 5||FileMonitor / Find Missing||public||2021-09-13 10:02||2022-11-29 20:09|
|Target Version||5.0.2||Fixed in Version||5.0.2|
|Summary||0018288: Deadlock: MM5 locks on startup and crashes on closing (regression 2501)|
|Description||MM5 locks on startup during File monitoring with deadlock and if I terminate File monitoring it crashes on close with log ID 62D60000 regarding UPnP|
I even tried to rename folder so that it is missing and that MM5 skips monitoring, even it is still accessible by Explorer, and MM access it without issues.
Full debug logs sent offline.
|Tags||No tags attached.|
|Fixed in build||2502|
||Peke, please provide more details + debug/freeze logs.|
||Updated Description, steps and sent logs offline.|
||This deadlock is actually the same regression as in 0018281 (introduced while fixing 0017895)|
||Fixed in 2502|
||Reopen, I got this error while testing MM service installation and service permissions.|
||Unfortunately no log file is created as service was started under "Local Service" permission which DBGView do not log.|
Based on the crash log it was assertion that MM5 wasn't closed within 10 seconds (this can happen only with debug build).
The reason was that MM5.DB couldn't be accessed during that time (most probably because you were testing the MM service at the same time that was accessing the same DB).
It is quite uncommon situation because normally either MM5 runs as service or MM5 is running (not both at once)
The issue for improving the error messaging re inaccessibility of MM5.DB is now tracked as 0019578