Issue metadata
Sign in to add a comment
|
Session restore fails on double-crash
Reported by
ericu@chromium.org,
May 12 2017
|
||||||||||||||||||||||||
Issue descriptionChrome Version : 59.0.3071.47 OS Version: Debian Jessie URLs (if applicable) : Other browsers tested: N/A What steps will reproduce the problem? 1. Kill Chrome [in my case by having X crash] 2. Restart Chrome; note the "restore tabs" button. 3. Before you can restore them, kill Chrome again. 4. Restart Chrome; note the lack of a "restore tabs" button. What is the expected result? I'd like to be able to restore my tabs, even if Chrome dies before I get the chance the first time around. What happens instead of that? As it is I can hunt through my history, but it's a mixture of stuff I visited and tabs I had open, in no particular order, and no grouped by window. It's actually easier for me to snag windows from my other devices, whose open windows are grouped nicely in the history UI, than it is to restore my old state. This just hit me again today, as I was debugging an issue with X. It's really annoying, as I usually have dozens of tabs in a bunch of windows, and some of them are quite long-lived. I'd maybe call this a feature request, but to me it feels like a bug in session restore, that it's so fragile. This may be the same as crbug/657727, but I'm not sure I'm reading that one right. Please provide any additional information below. Attach a screenshot if possible. UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.47 Safari/537.36
,
May 12 2017
,
May 12 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by brajkumar@chromium.org
, May 12 2017Labels: Needs-Feedback