View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005578 | MMW v4 | DB/FileMonitor | public | 2009-05-04 16:26 | 2010-11-01 15:35 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.1 | ||||
| Target Version | 3.1.1 | ||||
| Summary | 0005578: On restart of MM, library sometimes is completely empty | ||||
| Description | In some rare cases, restarting MM results in MediaMonkey not finding e.g. 1) Run MM and close it 2) I Installed debug version of 1242 and ran it (generating the attached debug log) --> DB appears empty! 3) Subsequent attempts to restart MM right away --> --> DB appears empty! 4) Approximately 5-10 minutes later, another attempt to restart MediaMonkey --> DB is populated again!! The reason why this is occuring is because somehow, a new .ini and DB is being created at: C:\Documents and Settings\NetworkService\Local Settings\Application Data\MediaMonkey\MM.DB Ludek has indicated that this is because some application changed the registry entry for \Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Local AppData . This is entirely possible because: -3 days ago I'd installed another application -In performing this test, MediaMonkey_debug was installed However, it doesn't explain the transient nature of the problem. | ||||
| Additional Information | Debug log of step 2 posted to ftp | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
It really looks that an application or malware changed the registry value. e.g. CCleaner does it, see: http://forum.piriform.com/index.php?s=6cdb58f3383aa1ef717a1229245c6459&showtopic=7919 but the real cause seems to be windows app called "USB Drive Letter Manager" as noted in the thread. We should add KB article related to this fact that the value \Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Local AppData can be changed from C:\Documents and Settings\Rusty\Local Settings\Application Data\MediaMonkey\MM.DB to C:\Documents and Settings\NetworkService\Local Settings\Application Data\MediaMonkey\MM.DB by another app and therefore MM appears empty. |
|
|
Closing. |
|
|
Note: another user observed this problem: http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=4685 |
|
|
Raising to urgent to try to determine repro steps. |
|
|
Based on description this looks very similar to bug 0005547 where we were able to replicate empty database creation. |
|
|
Raised to 'immediate' and assigned to jiri, since we already have a log and more info at 0005547. |
|
|
I don't see how to reproduce the issue, MM should behave deterministicaly on this, I don't see how could this problem happen. As for 0005547, there was a clear reason for the problem reported there, which was also fixed in 0005547, i.e. there doesn't seem to be any relation to the report in this issue. |
|
|
I guess, Rusty thought that if in 0005547 there is clear why it is happening and that we can inspect/optimize code to add more debug msgs to see why this happen. It happened me few times after update to new build but I've never been able to replicate each time. It happened me once again after testing SVN Build when I needed to use backup of library even size didn't change. |
|
|
It really seems that something rewritten the \Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Local AppData registry value as noted in my note 17678. It seems that we cannot do much about it - we should add KB article. |
|
|
This happened to me again today immediatelly after updating to the newest PrimoBurner SDKs and libs. I am not sure whether PrimoBurner could be the agent, but something changed the registry value \Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Local AppData from C:\Documents and Settings\<User>\Local Settings\Application Data\ to C:\Documents and Settings\NetworkService\Local Settings\Application Data\ So I would like to ask other members like Peke and Rusty to test build 1257 once is available. If the build cause the registry value to change then it would imply my theory that PrimoBurner could have an impact on this. |
|
|
KB article: http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=127 |
|
|
Setting as resolved, since it's documented now. |
