View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016920 | MMW 5 | General | public | 2020-09-08 11:21 | 2021-02-10 18:48 |
| Reporter | Ludek | Assigned To | |||
| Priority | immediate | Severity | crash | Reproducibility | have not tried |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0016920: Various crashes because insufficient system disc space | ||||
| Description | Based on crash logs (e.g. 058F0000) if the system disc gets out of space, then: - MediaMonkey.ini fails to write with EWriteError: Stream write error - writing to SQLite DB freezes in ntdll.dll -> ZwWriteFile - playback freezes while decoding because of freeze in ntdll -> ZwReadFile We can hardly predict all various crashes caused by insufficient disc space. Solution would be to show warning on MM5 start when there is insufficient space available in the MM data directories. Something like: Directory C:\User\Ludek\AppData\Roaming\MediaMonkey5\ gets out of space. Please free the C:\ disc space and try again. [OK] As the required quota we could use at least something like 200 MB ? | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2267 | ||||
|
|
Assigned to Rusty for wording of the message. |
|
|
I would suggest at least size of MM5.DB. Also it could be useful to check DB backups as last time I checked "Roaming\MediaMonkey 5\" was 17GB and that we push 0016176 fix to 5.0 (especially as Ludek updated ZIP libraries due the other bug fixes. Not sure if encoding is available or just decoder) or possibly add maintenance to delete old DB files. |
|
|
Good point with the DB backups, but size of MM5.DB isn't the only aspect, e.g. caching of looked up artwork (and artist images) also can take a lot of disc space. Caching of artist images is the default (while DB backups are optional AFAIK) I used this message in 2267 : https://www.dropbox.com/s/x0f0bvviyodjgjg/screenshot%202020-09-10%2014.33.24.png?dl=0 So the new strings to translate are: 'Directory %s gets out of space.' 'Please free the disc space for MediaMonkey to function properly.' I used quota 500 MB for the warning to show. |
|
|
Resolved for testing in 2267, then to be assigned to Rusty for the wording review. |
|
|
New wording applied in 2267: 'Drive %s is running out of space.' 'Please free up space for MediaMonkey to function properly.' |
|
|
Could the message include that MediaMonkey recommends to have at least x MB of free space on the drive? |
|
|
There isn't any value to recommend, it all depends on many unpredictable factors, e.g. - how many artist images is going to be downloaded/cached - how many streaming content is cached and where (Options > Player > Streaming > Maximum cache size) - how many auto-converted files is cached when sharing media (Options > Media Sharing > Maximum cache size) - how often user uses the backup DB feature (Manage Database > Backup database now...) and how big is his DB etc. etc. The point of this issue was just to inform the user that the system disk is running out of space (to prevent from submitting various crash logs as a consequence of the insufficient disk space). |
|
|
Verified 2270 in simulation of low disk space. As wording is corrected and there is not much We can do to estimate amount of space needed fr MM operation, but we now present user with warning MSG I would consider it closed? |
|
|
Resolving. The current fix is fine. Please verify that the warning appears when it should. |
|
|
Verified 2305 by user in remote session before we moved DB to other drive. Re verified by me using VM and lowering HDD space to trigger warning |
