Chat Backups are inflated in size

[SebiderSushi]

• I have searched open and closed issues for duplicates
• I am submitting a bug report for existing functionality that does not work as intended
• I have read https://github.com/signalapp/Signal-Android/wiki/Submitting-useful-bug-reports
• This isn't a feature request or a discussion topic

---

Bug description

When creating backups using the "Chat backups" feature the resulting backup files don't appear to be deduplicated. They can be vastly bigger than the actual data used by the Signal app. Forwarding messages inflates backup size while Signal App Data Size does not change.

Steps to reproduce

• Send a large-ish file or media (a couple megabytes)
• Create a backup and note down: Backup size & Signal app data usage
• Forward the file one or more times
• Create another backup, then compare backup sizes & Signap app data usage

Actual result: The Backup file size increases by the size of the forwarded file while Signal App usage does not. For example, in the case of another persons Signal i observed 400MB of app data usage while the backup file size was about 1GB.
Expected result: If Signal deduplicates forwarded messages internally they should also be deduplicated in backup files. The backup file should not be considerably larger than Signals app data.

Device info

Device: Xiaomi Redmi 4X
Android version: LineageOS 15.1 based on AOSP 8.1.0
Signal version: 5.18.5

Link to debug log

https://debuglogs.org/bb268c5fb8102c6c3430235813b64721c100dec8c3ac8dfe71885073a2133fc1

[SebiderSushi]

Replying to a message of a large file/media has the same effect.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[SebiderSushi]

This is reproducable with the current Signal version 5.29.7
This issue is being blocked by the fact that no one considered this issue when implementing backups and even now there is no one available to review it among the 1.3k open issue at the moment.
There is nothing any user can do to help it move forward.

Thanks for trying though, stale bot. /s

[stale]

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.

[SebiderSushi]

This is reproducable with the current Signal version 5.34.5

[stale]

This issue has been closed due to inactivity.

[SebiderSushi]

i guess it could be argued that this should not be discussed as a github issue as per this rule from #7598

If you disagree with the way that a feature is working (but it's working!) that's not a bug.

i would disagree because issues like this are part of the reason signal backups are much larger than necessary. as a result, i do not create any signal backups because i don't have the storage on my phone to store them. in my experience, this is equivalent to a feature that is not working; i am unable to create any signal backups at all even though i have enough storage on my PC. Signal does not offer any way to create useful backups on external / could storage unless you have lots of excess storage on your phone and copy huge monolithic backups every day.

i have no hope that this set of issues will ever be resolved (given its history of only making baby steps every now and then over multiple years). here's some relevant forum threads that i could find for anyone else reading this issue:

• https://community.signalusers.org/t/some-form-of-incremental-backup/12047
• https://community.signalusers.org/t/massive-amount-of-redundant-data-in-the-backup/18423/4
• https://community.signalusers.org/t/media-duplicated-with-quote-feature/3999/21

[cody-signal]

Hey there, we have an idea as to why this is happening, and tracking internally to fix.