Session restore after a crash is awesome and works nearly all the time but when it fails, the result is much worse that it should be. Not only do have lose all the open tabs, we immediately sync "no tabs open" to the cloud, removing any chance of recovering state from there either.
I had 2 crashes recently where the entire system locked up and session restore failed. In both these cases it failed entirely and I was left poking around with strings and grep to recover my tabe (in today's crash even that is not helping).
It seems we could do better. For synced sessions we can notice that the cloud says we have 20 tabs open but the local disk has none (or even visibly has corruption) and offer to restore from the cloud. It would lose history and forms but it would be far better than nothing.
More generally, it would nice if the on-disk state was more resilient to OS crashes, e.g. using a log-structured DB so that when some writes don't make it to disk, I get something. Maybe not the absolute latest state but a lot more than 0. Not trivial but maybe something to think about.
Comment 1 by sky@chromium.org
, Feb 8 2018