weird loss of -unsmushed backups

I think I found an operation path that leads to the loss of -unsmushed backups.
Here’s the procedure to reproduce it, it involves having three tabs open in the browser:

1) tab A: resmushit settings:  uncheck “optimize on unload”
quality 80

2) tab B, media library: load compressiontest.jpg, a large test jpg with almost no compression.
3) tab B, edit compressiontest: execute “optimize”
=> in tab C, check web file manager:
compressiontest-unsmushed is 800Kb
compressiontest is 160Kb 

4) tab B, edit compressiontest: CHECK “Disable of reSmush.it”
=> in tab C, check web file manager:
compressiontest-unsmushed is 800Kb
compressiontest is 800Kb (restored from -unsmushed)

5) tab B, edit compressiontest: UNCHECK “Disable of reSmush.it”
=> in tab C, check web file manager:
compressiontest-unsmushed is 800Kb
compressiontest is 800Kb 

6) tab B, edit compressiontest:  execute “optimize”
=> in tab C, check web file manager:
compressiontest-unsmushed is 160Kb
compressiontest is 160Kb 

Both files have the small size! The “unsmushed” file is actually smushed.

If I do:
4′) tab B, edit compressiontest: reload
6′) tab B, edit compressiontest:  execute “force re-optimize”
=>no problem

If I do:
4′) tab A, resmushit settings:  quality 40
5′) tab B, edit compressiontest: reload
6′) tab B, edit compressiontest:  execute “force re-optimize”
=>no problem

I know it’s definitely an edge case, but drove me crazy for hours, resmush.it was behaving very, very strangely.

Can you confirm this?

Thank you!

• This topic was modified 3 years, 11 months ago by Cyberchicken.