Chrome "did not shut down properly" message (sometimes) when resuming from Sleep mode
Reported by
loupi...@gmail.com,
Feb 6 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. Have a Chrome browser window opened 2. Enter sleep mode 3. Resume from sleep mode What is the expected behavior? The chrome window(s) and tabs should reappear the way they were before sleep mode. What went wrong? On occasion (about 10-20% of the times), a Chrome window appears without all the previously opened tabs, and the pop-up "Chrome did not shutdown properly - Restore". Clicking on Restore brings back all the Chrome tabs and windows that were opened before the system was put in Sleep mode. It looks like Chrome crashed either at the time the system entered Sleep mode, or when it resumed from Sleep mode. Crashed report ID: How much crashed? Just one tab Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 56.0.2924.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0 This issue seems random, cannot be reproduced, but happens quite often.
,
Feb 6 2017
,
Feb 6 2017
I think you can close this thread. The issue has been traced to an issue causing my Windows 10 to sometimes do a "regular" reboot when resuming from Sleep mode, presumably because it could not do a normal "resume" (maybe due lost or corrupted memory). The Windows config that I have starts Chrome as a start-up program upon regular system boot, so when Chrome starts, it displays the "did not shut down properly" message, which is normal because Windows 10 did a reboot but was not shutdown (it was previously put into "Sleep" mode with Chrome running. So the issue is with Windows 10 sometimes doing a reboot when resuming for Sleep mode. Not a Chrome issue.
,
Feb 6 2017
A google search for "windows 10 reboots after sleep" yields more than 1 million results, so it seems to be a wide spread issue with likely various causes...
,
Feb 6 2017
As per the comment #3 closing this issue. Please feel free to raise a new issue if you face any issue on chrome. Thanks,
,
Feb 7 2017
thanks! |
|||
►
Sign in to add a comment |
|||
Comment 1 by loupi...@gmail.com
, Feb 6 2017