View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003047 | MMW v4 | DB/FileMonitor | public | 2007-05-10 19:25 | 2007-05-30 20:24 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | unable to reproduce |
| Status | closed | Resolution | unable to reproduce | ||
| Summary | 0003047: MM-DB Journal file causes MM to freeze | ||||
| Description | This issue was reported by a user: when the user runs MM, the app freezes. When they delete the journal file, then it starts working correctly. As requested by Jiri, the db and journal from the user have been provided and are now saved to the ftp server. | ||||
| Additional Information | > ----- Original Message ----- > Hi Russell, > > > > Two minutes earlier I was send a report regarding the frozen MM3. > > I put this text in it > > > > "There are a lot of issues with the DB (+34000 tracks). > > By Startup MM3 is trying to read the tracks and then seems to be > frozen. > > When I look in the folder where the database is stored I see a > MM.DB-journal file (3kb). > > When I removed a previous session with the same problem this file and > the MediaMonkey.ini file, by new restart everything was normal and MM3 > could read all the tracks again. > > I will try to delete now only the MM.DB-journal file and hope that > deleting the config file is not necessary because otherwise I need to > redo every time all the settings. > > I will send an e-mail to Russell too with this remark. Regards Erik" > > > > I can confirm that MM3 started normal once the file MM.DB-journal was > deleted in the MediaMonkey folder in Application Data. > > I hope this is helpful for you to resolve this problem. > > > > Regards, > > Erik | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
