MediaMonkey Portable crashes badly when USB is disconnected
Posted: Sun Aug 04, 2013 5:53 pm
Hi,
I'm using MediaMonkey v4.0.7.1511 Portable Edition on Windows 7 x64.
If the USB drive that runs MediaMonkey becomes disconnected (e.g. someone knocks the cable, or some other hardware device causes the USB port to reset), then MediaMonkey will throw up numerous error messages similar to the following:
"There was a problem querying the database:
Could not retrieve data "SELECT * FROM Filters WHERE ID=?" : disk I/O error (10, 10)"
The error pops up multiple times along with other similar messages. MediaMonkey almost never recovers from this error, and makes no attempt to restore it's connection to the drive even after it has been reconnected. You can rarely dismiss all the messages, and often the only way to shut down MediaMonkey after such an error is to kill it via the Task Manager.
Given that USB drives are inherently prone to being disconnected occasionally, I would like to suggest MediaMonkey handles these sort of I/O errors more gracefully. The user should at least be able to dismiss the error message and shut down MediaMonkey through the normal procedure without having to resort to Task Manager.
Thanks.
I'm using MediaMonkey v4.0.7.1511 Portable Edition on Windows 7 x64.
If the USB drive that runs MediaMonkey becomes disconnected (e.g. someone knocks the cable, or some other hardware device causes the USB port to reset), then MediaMonkey will throw up numerous error messages similar to the following:
"There was a problem querying the database:
Could not retrieve data "SELECT * FROM Filters WHERE ID=?" : disk I/O error (10, 10)"
The error pops up multiple times along with other similar messages. MediaMonkey almost never recovers from this error, and makes no attempt to restore it's connection to the drive even after it has been reconnected. You can rarely dismiss all the messages, and often the only way to shut down MediaMonkey after such an error is to kill it via the Task Manager.
Given that USB drives are inherently prone to being disconnected occasionally, I would like to suggest MediaMonkey handles these sort of I/O errors more gracefully. The user should at least be able to dismiss the error message and shut down MediaMonkey through the normal procedure without having to resort to Task Manager.
Thanks.