New issue
Advanced search Search tips

Issue 757212 link

Starred by 6 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

After update to 62.0.3188.4 Chrome became consume all CPU resources

Reported by mikhail....@gmail.com, Aug 20 2017

Issue description

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

Steps to reproduce the problem:
1. 
2. 
3. 

What is the expected behavior?

What went wrong?
Google Chrome consume all CPU resources

Did this work before? N/A 

Chrome version: 62.0.3188.4  Channel: dev
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 27.0 r0
 
chrome.dmp
3.5 MB Download
Скриншот 20.08.2017 14-18-25-255.png
68.1 KB View Download
I found this issue specifically on Gmail. Just open Gmail and after a few seconds it starts to consume one whole core of CPU.
Soon after my previous comment I found a couple of Twitter pages were also inhabited, and they apparently only do this while being backgrounded.
Скриншот 21.08.2017 10-06-27-469.png
102 KB View Download
for workaround problem is enough to open tabs one by one that caused the processor load.

Demonstration: https://youtu.be/-IgtIlBC2a0

Comment 6 by ajha@chromium.org, Aug 22 2017

Cc: ajha@chromium.org
Labels: Needs-Feedback
Tested this manually, over installing the latest Dev(62.0.3188.4) over the previous Dev(62.0.3178.0) on Windows-7 with signed in Chrome account and didn't encounter any such CPU spike. Attached is the screenshot of the task manager.


mikhail.v.gavrilov@: Is this spike in CPU specific to any profile or happens with every profile? Try disabling extensions and see if there is any difference here.

757212.png
1.9 MB View Download

Comment 7 by ajha@chromium.org, Aug 22 2017

Labels: Needs-Triage-M62

Comment 8 by tomm...@gmail.com, Aug 22 2017

For me, CPU spiking and lagging happens (mostly) when dev tools is open.

I updated Chrome today and just after few hours I started noticing weird lagging while working (laggins is most noticeable when selecting an element on 'Elements' tab).

All extensions disabled and only 1 tab open (see screenshots).

I'll try downgrading when I have a chance.

In the meanwhile I tested with Vivaldi browser and, for example, selecting an element is much faster/snappier.
Vivaldi UA (Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.105 Safari/537.36 Vivaldi/1.92.917.43)

Okay, Vivaldi is based on Chromium, so it's not exactly the same but nevertheless.

Is there any logs/dumps we could provide to make diagnosing easier?

PS. I should also mention that my dev PC isn't really top notch, so slight drops on performance is usually quite noticeable to me.

Versions & UA:
62.0.3188.4 (Official Build) dev (64-bit) (cohort: Dev)
V8 6.2.265
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3188.4 Safari/537.36
crbug-chrome-cpu-spiking.jpg
173 KB View Download

Comment 9 by c4des...@gmail.com, Aug 22 2017

Same has been happening here, especially with sites like youtube. I tend to preopen like 5-6 or even more on a new page and just when I start a single video the CPU usage goes to 100% with each youtube page consuming a lot even though I haven't even loaded them.

Windows 10 (Build 14393.447)
Version 62.0.3188.4 (Official Build) dev (64-bit)
chrome_cpu_usage.png
30.7 KB View Download
Reporter@: Could you please confirm that the issue has resolved since the issue is in #62.0.3188.4 dev and latest dev got upgraded.
Thanks!
Yes, issue was gone.
Project Member

Comment 12 by sheriffbot@chromium.org, Nov 24 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "ajha@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
As per Comment #11,marking this issue as Wont-Fix.
Thanks..

Sign in to add a comment