View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003909 | MMW v4 | Synchronization | public | 2007-11-05 00:15 | 2007-11-12 20:47 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | unable to reproduce |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.0 | ||||
| Summary | 0003909: wmdm synchronization fails to terminate | ||||
| Description | User reported the following--I've posted the logs to the ftp server: When I try to synchronize to my archos 605 media player, the process starts and the progression bar progresses but when it gets to the end it does not complete and end / close the process. It continues to state "synchronizing the a605" in the progression meeting even though it should be complete. I can disconnect my player and it is appears fine. In this state, MM is responsive and appears fine - i.e. I can play tracks, etc… If I right click on the bar, it gives me the option to terminate the process. However, selecting that option has no effect. If I try to close MM, it tells me that "There are background processes running. Terminate them?" (yes / No). If I select “yes” is closed, but the right side of the task bar shows that it is still running and if I open the window’s task manager it shows that mediamonkey.exe is running. If I terminate the process, I can get it to close. However, this has the effect of sometime corrupting the MM database and opening MM and attempting another sync, generates a sql error. This is consistent and reproducible. …I have been through the process of deleting and rebuilding the db, attempting the first sync, have is “get stuck”, terminating and trying again, having the db now corrupted (with the only solution to be to delete and rebuild the database. Attached is the debug log. I did a simple sync with a single album. near the end when it was in the non terminating loop, I tried to close and then accepted terminate processes. Please let me know if there is anything else I need to collect. Thanks. Please help, I love the application and have upgraded to gold already. I started using MM two revisions ago (1091 if I remember correctly) and did not have the sync issue. I am running Vista on and Intel processor. Not sure what to collect of how to collect it to help the developers resolve this. Please let me know and I will assist though. Thanks. Originally reported by rskillic (same user) at: http://www.mediamonkey.com/forum/viewtopic.php?t=22291 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1100 | ||||
|
|
Fixed in build 1099. - I can't reproduce either, but based on the description I see only one possible reason - a small change in threading model made recently. I tried to revert it back, it should help. |
|
|
rskillic tested build 1099 and reported the following (note: I'm posting his updated log to the ftp server. I've also requested that he perform the sync with a clean db): failed, but it a little different. This time the failure came back as the There was a problem querying the database: Error executing SQL statement "UPDATE DeviceTracks SET Status=1 WHERE IDDevice=? AND IDTrack=?" : unable to open database file (14, 14) you can see this in the logs starting at : 00076368 72.46913910 I ran this on the existing 1091 database. note that there is nothing to sync since I have not added any music of changed any album attributes. after I got the error, I closed the dialog box and exited the application. Next, I opened 1091 and the sync was fine. ...for good measure I ran the 1099 again and got the exact same failure. two comments: 1) I notices on 1098 that when I would try to sync it would freeze and I would have to force close via vista (like stated). but then if I tried again, I would get the error 14,14 - just like I got on the 1099. I assumed I was seeing a database corruption, but maybe not???? 2) should I try syncing on a fresh build of the database from 1099? i.e. is there any database structure change??? ..again, going on the same database with 1091 immediately afterword works fine. |
|
|
Assigning back to Rusty to find out as much as possible from the user - unfortunatelly using the log I can't find the source of the problem. The best would be if the user could check out which build introduced the problem. |
|
|
Fixed in build 1100. - All threading model issues should be resolved now. |
|
|
Verified 1101--no regressions. |
