View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006672 | MMW v4 | DB/FileMonitor | public | 2010-11-10 15:52 | 2010-11-10 15:55 |
| Reporter | lowlander | Assigned To | |||
| Priority | none | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Product Version | 3.2.2 | ||||
| Summary | 0006672: When DB becomes unavailable MediaMonkey hangs | ||||
| Description | This issue can occur when users have DB on the network or portable drive that becomes unavailable while MediaMonkey is running. MediaMonkey will start generating error messages and require a shutdown from the Task Manager. It might be wise that when SQL errors occur that MediaMonkey verifies the DB is still accessible and in case it isn't that MediaMonkey prompts the user that the database is unavailable. This prompt should auto-monitor for the DB becoming available again (user reconnects it) as well as offer user to exit MediaMonkey. Another option that could be added is to offer to restart MediaMonkey which would recreate a new database. | ||||
| Steps To Reproduce | 1) Store DB on network or portable drive 2) Start MediaMonkey 3) Play some tracks 4) Disconnect the location where the DB is located | ||||
| Additional Information | http://mediamonkey.com/forum/viewtopic.php?f=7&t=33302 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
