Issue metadata
Sign in to add a comment
|
Unable to re-restore webpages when chrome or computer disabled/cutoff/crashed during recovery process
Reported by
c933...@gmail.com,
Jan 17 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Steps to reproduce the problem: 1. Open a few hundreds or a few thousands tabs (the amount of tab needed depend on performance of the machine that the browser run on, the bug would be reproducable as long as there is a reasonably lengthy time needed during the tab restoration process) 2. Force Close Chromium 3. Relaunch chromium 4. Click on the prompt that ask you whether you want to recover 5. Cut off the power of the computer or kill the chromium process or the windows login process or in any otherway interrupt the recovery 6. Relaunch chromium 7. press the recover button What is the expected behavior? Those tabs should be restored as original What went wrong? Only some of the original tabs are restored Did this work before? No Chrome version: 63.0.3239.132 Channel: stable OS Version: 6.3 Flash Version: N/A I have encountered similar situation in previous chrome for android versions too
,
Jan 17 2018
,
Jan 23 2018
Unable to reproduce the issue on reported chrome version 63.0.3239.132 and on the latest canary 66.0.3329.0 using windows 10 with the below mentioned steps. 1. Launched Chrome and opened around 40 tabs 2. With tabs of search results "chrome://version, crbug.com, a.b,c,...z, 1,2,..10, test, final and end" 3. Force closed chrome 4. Relaunched Chrome 5. Clicked on Restore We observed all the tabs restored properly with out any missing tabs. Attaching the screencast of the same. @Reporter: Could you please check the screen cast and let us know if we have missed any step while reproducing the issue. Any further inputs from your end may help us to triage the issue in a better way. Thanks!
,
Jan 23 2018
- Please re-read the reported step, it should involve killing the chrome in the tab restoring process, as in, after clicking the restore button, before all tabs appear on the tap bar, the chrome is to be killed, instead of during normal operation status - As, according to the screencast, the 40 tabs are almost instantaneously restored, that mean 40 tabs is not enough to reproduce the bug. When I encounter the problem, I was having about 850 tabs opened. Please consider using this order of magnitude amount of tabs in reproduction. Also, that is when my system hardware is an eMMC NAND storage and a Pentium CPU which might limit the restoring speed. If your system has a faster hardware which made the restoring process instantaneous, which make it hard to kill the chrome right when the tabs are being restoring, then please consider adding more tabs in the test.
,
Jan 23 2018
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 23 2018
As per comment #4 we are unable reproduce this issue on reported chrome version 63.0.3239.132 using windows 10 & 7. We have tried with 60+ tabs but unable to reproduce from our end. Hence adding ui>browser>Sessions component to this issue. Requesting someone from the respective team to help in further debugging this issue. Thanks.!
,
Jun 21 2018
Adding label "TE-NeedsTriageHelp" as we are unable to reproduce the issue from our end (...as mentioned in C#6)and requesting someone from UI>Browser>Sessions team to have a look into this and help in further triaging it. Thanks!
,
Jun 21 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by c933...@gmail.com
, Jan 17 2018