New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 671075 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Heavy CPU usage after restoring of background tab

Project Member Reported by borisv@chromium.org, Dec 5 2016

Issue description

Chrome Version: 
OS: OSX 10.12.1

What steps will reproduce the problem?
(1) Open a few tabs
(2) Make sure that one of the tabs is this one: http://this.deakin.edu.au/culture/car-wars
(3) Set your browser to restore the tabs and select another tab than the one above.
(4) Close Chrome and launch it again

Observe the CPU usage: Chrome hits 100% CPU usage (fans get really noisy, etc) with almost all of it coming from the tab that has http://this.deakin.edu.au/culture/car-wars open.

What is the expected result?
No observable CPU increase.

What happens instead?
Huge impact on the CPU usage and my laptop power.

I cannot reproduce this 100% of the time, but I grabbed sampling reports. See the attached files.
 
Google Chrome Helper Heavy CPU_1.txt
400 KB View Download
Google Chrome Helper Heavy CPU.txt
277 KB View Download
Forgot the Chrome version: 55.0.2883.75
Components: Blink>MemoryAllocator
Labels: M-55
Cc: rsch...@chromium.org
Labels: Performance
Can you also take an about:tracing trace of the bad behavior?
The problem is difficult to reproduce, but I will make sure that I get the about:tracing trace the next time it happens.
Labels: -Pri-3 Pri-1
I'd like to get to the bottom of this, upping priority for now. Once we have some reasonable hypothesis, let's keep on this.
Labels: prestable-55.0.2883.75
Here is the symbolized output of one of the traces above. Let me know if you are interested in the symbolized trace of the other trace that I took.
GoogleChromeHelperCPUSymbolized.txt
471 KB View Download
Labels: -Pri-1 -Performance Performance-Loading Pri-2
Status: Available (was: Untriaged)

Comment 9 by nduca@chromium.org, Apr 27 2017

Labels: Hotlist-GRC
I just hit it today and tried to collect a couple of traces. v57.0.2987.133. It burned 25% of my battery in ~20 min. The fan spinning like crazy and the laptop getting really hot. Note that activity monitor showed that "kernel task" takes 280% CPU for a while then Chrome took over as being the major consumer.
trace_RightAfterCPUCrunch.json.gz
4.8 MB Download
trace_Continuous.json.gz
7.8 MB Download

Comment 11 by tasak@google.com, Apr 27 2017

Looking at trace_RightAfterCPUCrunch.json.gz, MemoryCoordinator::onMemoryPressure was invoked. So chrome spent too much memory, and MacOS was probably under critical memory pressure status... The memory pressure status caused 280% CPU usage.

So would you run trace with memory-infra? If possible, run chrome with --enable-heap-profiling.

I would like to know activity monitor's memory usage too. Probably some renderers' compressed memory usage was too large.


I plugged the machine in and closed the lid. Instead of going to sleep the machine started spinning the fan like crazy for several minutes. When I opened the lid again, the screen remained blank and eventually the laptop shut itself down. Everything seems ok after the restart. Something seems to be happening around going to/resuming from sleep.

Sure next time it happens, I will check the memory usage as well. I was focusing on the CPU this time.
Tab restoring seems to do the same. See the attached trace. I ran with --enable-heap-profiling.

trace_TabRestoring.json.gz
5.4 MB Download
Cc: nasko@chromium.org
Note that the bug is more typically hit when the machine comes out of sleep. At that point, the issue is so extensive that the whole system dies shortly after (black screen) and only forced shutdown recovers it. Activity monitor shows kernel_task using all CPU.

Adding Nasko@, as he mentioned that there was a recent thread about this issue. Nasko, can you loop in the folks on the thread? Hopefully the problem is better known now?
Owner: erikc...@chromium.org
Erik, can you take a look at the traces. This sounds like a common problem.
Cc: -rsch...@chromium.org
Status: Assigned (was: Available)

Sign in to add a comment