View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0021781 | MMW 5 | Other | public | 2025-09-23 15:01 | 2025-09-29 13:31 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 2024.2 | ||||
| Target Version | 2024.2 | Fixed in Version | 2024.2 | ||
| Summary | 0021781: MediaMonkey crashes when backup destination is full | ||||
| Description | With Backup enabled, MediaMonkey crashes on startup if the backup destination doesn't have enough free space. | ||||
| Additional Information | Log 87380000 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3168 | ||||
|
|
OK, the question is what should happen in such a case.. By default there is Retain backups: [3] and currently the old backups are deleted only once the new backup is created.. We could solve it by deleting all but one backup despite the value configured, or (better case) add a warning --> which would require new strings to translate, so probably something for 2026 ? In either case whenever there isn't enough space to make a single backup then a message is needed anyhow, something like: There isn't enough space to backup database/settings, please clear space in the backup location: C:\... [OK] Assigned to Rusty for review.. |
|
|
1) Regardless of whether we add any new strings, MMW shouldn't crash in this case. 2) We can re-use existing strings for a generic message that applies to either 1 or multiple backups. e.g.: Backup FAILED! Insufficient space available. Please free up space for MediaMonkey to function properly. (Path: <backup path>) [Settings] [Cancel] |
|
|
Fixed in 3168 |
