Closing Chrome or Chromium-based applications causes Windows to lock up for a period of time
Reported by
ds84...@gmail.com,
Aug 19
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Steps to reproduce the problem: 1. Use either Chrome, Chromium, or a Chromium-based application (Discord, Visual Studio Code, for example) 2. Use it for some time without closing it (over the span of a couple of days typically, but I've been able to reproduce small lock ups after having Discord open for two days) 3. Close the application What is the expected behavior? Windows not locking up. I've always remembered having this problem on this laptop (Acer Aspire VX 15), but my friend has had the same problem on a laptop with similar specs. Both laptops have an Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz, which has an integrated Intel HD 630. Initially, I thought it was a problem with Intel's graphics drivers, but my friend runs everything on his Nvidia. What went wrong? After you close the application the mouse cursor will stop moving, indicating that Windows has locked up. For longer hangs, you'll notice that if you plug in a USB device it won't be noticed by Windows (no sounds, no flash drive accesses), Caps/Num Lock LEDs won't change, and for certain laptops the keyboard backlight can't be toggled. I've recorded an ETW trace during a small hang caused by closing Discord: https://u.pxtst.com/0yeh4gowtI_Pqn.etl In the trace, the hang happens after Discord isn't in focus where there are no mouse move events. Did this work before? N/A Chrome version: 68.0.3440.106 Channel: stable OS Version: 10.0 Flash Version: I can also record a trace of me closing Visual Studio Code and Chrome 68.0.3440.106.
,
Sep 7
ds84182@ Thanks for the issue... @Reporter: Could you please upgrade to latest chrome stable 69.0.3497.81, you can download latest chrome builds here:" https://www.chromium.org/getting-involved/dev-channel ". Let us know whether issue still persists and attach a trace if still seen on m-69 as well. Thanks.!
,
Sep 17
I just experienced the same freeze issue on that version, but this time I forgot to record a trace.
,
Sep 17
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 10
@Reporter: Could you please try to test this issue on latest chrome stable# 69.0.3497.100 and check if the issue still persists. If the freeze issue still happens, check whether the freeze leads to browser crash. If it crashes happens, provide the crash ID by navigating to chrome://crashes and also provide the trace of the latest chrome stable, which will helps us in further triaging it in better way. Note: You can download latest stable from URL: https://www.chromium.org/getting-involved/dev-channel. Thanks!
,
Dec 21
Crash report or trace not available. Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by susan.boorgula@chromium.org
, Aug 19