Silently keeps large (> 100 MB) file in %APPDATA%/Ditto/Dumps/Ditto.exe...dmp
While transferring Ditto, I realized that %APPDATA%/Ditto/ contained a Dumps/ directory with a 135 MB Ditto.exe.16708.dmp from 2024-07-31. This size probably matches the size of the database (Ditto.db is also 135 MB). Although Ditto backups in less than 10 MB, I imagine Ditto.db's size is normal/acceptable since I configured it to keep > 5000 entries.
I for one do not oppose keeping a dump after a crash, but I do find it problematic to silently keep such a large dump for more than a year. On a PC, that dump alone, which I had no use for, was occupying ~0.07 % of my SSD. Assuming the dump includes the database, there is also a security aspect to this; the database can contain sensitive clips like passwords. If the user has stopped working on a project and cleared his history, he does not expect old clips to remain on the drive.
I am unfortunately not sure which version I used when that file was created, but I would bet it was less than 2 years old. I currently use 3.25.113.0.
Some possible solutions/mitigations:
- Warn when starting after a dump was taken
- Warn when starting if Dumps/ exceeds 50 MB
- Warn when starting if a dump over 50 MB has been stored for more than 1 month