Comment 8 for bug 1883129

Sorry if this is tedious, but I thought it worth putting together all the data points in one place. I've included two new ones at the end.

Just to keep things clear, here's the terminology I'm using.

Original Machine: This is the computer that created the original large backup which is under discussion.

VM: This a virtual machine running on Original Machine.

Junky Machine: This is a computer I pulled out of the closet to test what's going on. It's running Ubuntu 18.04.3 LTS, Deja Dup 40.7 via snap.

(Old) Data point #1. (This is the original bug.) Backup made on Original Machine would cause the aforementioned crash when I attempted to restore on the VM.

(Old) Data point #2. Same backup made on Original Machine would appear to restore correctly on Original Machine.

(New) Data Point #3. To make sure the problem wasn't in my VM, I created a very small backup from the VM, performed it, and then restored it to the VM. That worked fine, no crash.

(New) Data Point #4. I pulled out Junky Machine from the closet and attempted to perform a restore on my original backup. Boy did it take a while, but it eventually got past where the VM was crashing. I let it restore a few files to make sure it was working and then canceled.

At this point, my best guess is that it's something about my particular backup AND the VM. Could it be the size of the backup is interacting with the VM? It's a very large backup. (~350GB)

Can I do anything else, or give you any additional information that would help you track this down? Obviously, on my end it's not critical. The backup appears to have worked and I seem to have several options for restoring. But, *something* isn't working correctly, somewhere...