Comment 21 for bug 1121169

Autosave overall seems to give similar results for 3.9.91 and the fix-cropping-slowness branch. In both cases, I scanned a single image and then terminated simple-scan with CTRL-C at the terminal. On restart, both versions found two copies of the scanned image and restored two indentical copies of the page.

Relevant output from the log:
[+0.04s] DEBUG: autosave-manager.vala:127: Found at least one autosave page, taking ownership
[+0.13s] DEBUG: autosave-manager.vala:572: Found a page that needs to be recovered
[+0.13s] DEBUG: autosave-manager.vala:588: Restoring a page of size 2549 x 3506
[+0.21s] DEBUG: autosave-manager.vala:624: Updating autosave to point to our new copy of the page
[+0.31s] DEBUG: autosave-manager.vala:572: Found a page that needs to be recovered
[+0.31s] DEBUG: autosave-manager.vala:588: Restoring a page of size 2549 x 3506
[+0.34s] DEBUG: autosave-manager.vala:624: Updating autosave to point to our new copy of the page
[+0.44s] DEBUG: autosave-manager.vala:393: Adding an autosave for a new page
[+0.54s] DEBUG: autosave-manager.vala:495: Updating the pixels in the autosave for a page
[+0.66s] DEBUG: autosave-manager.vala:393: Adding an autosave for a new page
[+0.76s] DEBUG: autosave-manager.vala:495: Updating the pixels in the autosave for a page
[+0.90s] DEBUG: autosave-manager.vala:445: Updating the autosave for a page

Only in the fix-cropping-slowness branch, I see the following lines upon clean exit:
[+33.02s] WARNING: autosave-manager.vala:209: Failed to delete autosave file
[+33.02s] WARNING: autosave-manager.vala:209: Failed to delete autosave file
[+33.02s] WARNING: autosave-manager.vala:209: Failed to delete autosave file