View Issue Details

IDProjectCategoryView StatusLast Update
0019578MediaMonkey 5DB / Backuppublic2022-11-29 20:09
ReporterLudek Assigned To 
PriorityurgentSeveritymajorReproducibilityhave not tried
Status feedbackResolutionopen 
Product Version5.0 
Target Version5.1 
Summary0019578: Improve error handling when DB cannot be accessed
DescriptionCurrently when DB cannot be accessed then Debug builds generates crash log -- which does not say nothing to users about the reasons.

- Rusty observed 0019559 where DB couldn't be accessed because of Disk I/O error
- LowLander observed crash when his M.2 drive loses drive letter. This caused MM to not have access to the DB on the drive.

Looking at the errors that could be handled that way (to be shown with message dialog + Retry button):
  SQLITE_BUSY = 5; // The database file is locked
  SQLITE_LOCKED = 6; // A table in the database is locked
  SQLITE_READONLY = 8; // Attempt to write a readonly database
  SQLITE_IOERR = 10; // Some kind of disk I/O error occurred
  SQLITE_CANTOPEN = 14; // Unable to open the database file
  SQLITE_NOTADB = 26; // File opened that is not a database file

I think that for all these errors we could show a common dialog like:
"Database file %s cannot be accessed."
"Error" <<error code>>
[Retry] [Cancel]

Note that "Database file %s cannot be accessed." would be a new string to translate. As "Error" already exists.

TagsNo tags attached.
Fixed in build

Relationships

related to 0019559 closedLudek Crash A35A0000 after testing auto-tagging (Disk I/O error) 
related to 0018288 resolvedLudek Deadlock: MM5 locks on startup and crashes on closing (regression 2501) 

Activities

Ludek

2022-11-21 19:56

developer   ~0070418

Assigned to Rusty to review the wording.