Windows froze completely with Chrome saying "Waiting for cache.."
Reported by
hjlamb...@gmail.com,
Jan 3 2018
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 Steps to reproduce the problem: Haven't been able to reproduce the issue What is the expected behavior? What went wrong? Upon expanding an image on reddit using the RES extension, my entire computer locked up. Nothing happened on screen, my mouse wouldn't move, ctrl+alt+del didn't work, and there was no indication whatsoever that the processor was still doing anything (no fan noise etc.). Not even hitting the power button to get to sleep mode worked. While this happened, Chrome was displaying the message "Waiting for cache.." in the bottom of its window. After not having anything happen for about an hour, I shut it down by holding the power button. In my administrative events I just see that it hadn't anticipated the shutdown. No events whatsoever were generated at the start of or during the lock. Chrome also failed to produce any kind of error log. I imagine this may not be a Chromium issue at its core since it managed to seemingly kill windows/the processor off, but I figured I'd share just in case since the freeze did seem to be triggered by Chrome. There also seem to be somewhat similar reports online of computers hanging while displaying the "Waiting for cache" message. I've not experienced any unexpected hangs like these outside of this one event, and I'm using relatively new hardware. Did this work before? N/A Chrome version: 63.0.3239.84 Channel: n/a OS Version: 10.0 Flash Version:
,
Jan 4 2018
Thanks for the report. I'm going to mark this as WontFix for now, because there's not really much actionable information for something like this. Checking the Event Log is spot on the right thing to do - but it's perhaps unsurprising there weren't details. While not specific to Chrome, events such as this have been triggered in the past by bad drivers or bad antivirus. If you have antivirus, I would make sure it's running the latest version, and would recommend running Windows update to make sure you've got the latest drivers as well. If it happens again, would you file a new bug and mention this? If it becomes a trend and/or reproducible, then it becomes something that we can look into debugging more. Thanks for attempting to help make Chrome a better browser! |
||
►
Sign in to add a comment |
||
Comment 1 by krajshree@chromium.org
, Jan 3 2018