New issue
Advanced search Search tips

Issue 816532 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 770201
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome slow after sleep on Win 10

Reported by ras...@mindplay.dk, Feb 26 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36

Example URL:
https://google.com/

Steps to reproduce the problem:
1. Install VMWare
2. Open Chrome
3. Put computer to sleep
4. Chrome is extremely slow and maxes out one CPU core (e.g. continuous 25% CPU usage on a quad-core CPU)

It's slow enough to make the computer unusable, and rebooting the system is necessary to restore things to normal.

What is the expected behavior?

What went wrong?
This affects the browser in general, it's not specific to any website as far as I can tell.

Problem started for me with the recent major Win 10 update, so about a month ago - although I suppose the issue could have started with a Chrome update release around the same time.

Others have been reporting this problem since June 17, so it may have existed for much longer, or there may have been a regression:

https://productforums.google.com/forum/#!msg/chrome/lPSzwq4N1Z0/3y2fx4I7BAAJ

Other affected users have reported removing all extensions, so this does not appear to be caused by an extension. (I haven't tried that myself, as the problem was resolved by the work-around described below.)

Disabling all VMWare virtual network interfaces resolved the problem for me. (I will leave VMWare installed - if you'd like me to re-test for this issue, I can enable them again. The issue is readily reproducible.)

While this is happening, I've noticed the "downloading proxy script" notice at the bottom of the browser.

Other applications (include Edge and Firefox) do not exhibit any similar problems, so this must be specific to something unusual that only Chrome is doing with the network - perhaps scanning the network interfaces for some reason? I can't provide a better guess.

Did this work before? N/A 

Chrome version: 64.0.3282.186  Channel: stable
OS Version: 10.0
Flash Version:
 

Comment 1 by mmenke@chromium.org, Feb 26 2018

Cc: eroman@chromium.org
Components: -Internals>Network Internals>Network>Proxy
Labels: Needs-Triage-M64

Comment 3 by eroman@chromium.org, Feb 26 2018

Mergedinto: 770201
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment