Daily backup hogs all storage even if it will fail the backup
- [x] I have searched open and closed issues for duplicates
- [x] I am submitting a bug report for existing functionality that does not work as intended
- [x] I have read https://github.com/signalapp/Signal-Android/wiki/Submitting-useful-bug-reports
- [x] This isn't a feature request or a discussion topic
Bug description
System instability during daily backup, the process ends up hogging all storage daily and crashing other apps in the process DESPITE there being nowhere enough memory to complete the backup.
Steps to reproduce
- Have 2GB of chat data
- Have an existing backup with daily backups turned on for say 14:00.
- Have less than 1 GB left of primary system memory
Actual result: Backup will start around 14:00, resulting in 0 bytes of primary storage will be left until the process decides that it has failed and releases disk space. Expected result: Backup terminates before it even starts hogging space if there is not enough space on the primary drive.
Screenshots
N/A: Cannot do screenshots when there isn't space on the primary drive.
Device info
Device: XQ-AS52 Android version: 12 Signal version: 7.13.4
Link to debug log
N/A: Cannot get link until memory is cleared
Since the backup are rotated during the procedure, you also need double the free space required for a single backup (which can become huge after some time, lots of received media etc). The system can become pretty much unusable by this behavior.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been closed due to inactivity.