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

Issue 827788 link

Starred by 1 user
Status: Duplicate
Merged: issue 834421
Owner:
sadrul@chromium.org
Closed: Apr 2018
Cc:
█ sindhu.chelamcherla@chromium.org
creis@chromium.org
wfh@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

After roughly 20, 30 mins of browsing CPU goes up over 100% - only restart helps

Reported by off...@mikemitterer.at, Mar 31 2018 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Steps to reproduce the problem:
No way. Only happens after ~30 mins

What is the expected behavior?

What went wrong?
Takes to much CPU power

Did this work before? N/A 

Chrome version: 65.0.3325.181  Channel: stable
OS Version: OS X 10.11.6
Flash Version: 

This happens since a few weeks. Never had problems like this before
CapturFiles-20180331_123730.png
1018 KB View Download

Comment 1 by woxxom@gmail.com, Mar 31 2018 

Can you reproduce the bug in a new browser profile without extensions?

Did you change anything in chrome://flags ? 
If so, try clicking "Reset all to default" on that page.

Also, it'd be helpful if you record a tracing profile when that happens next time:
1. open chrome://tracing/
2. click "Record"
3. click "Manually select settings"
4. click "All" (on the left)
5. click "Record" at the bottom
6. wait for 5-10 seconds
7. stop, wait for the UI, then click "Save", zip it and upload here

Comment 2 by vamshi.kommuri@chromium.org, Apr 1 2018

Labels: Needs-Triage-M65

Comment 3 by sindhu.chelamcherla@chromium.org, Apr 3 2018

Cc: sindhu.chelamcherla@chromium.org
Labels: Needs-Feedback Triaged-ET
As per comment#1 adding Needs-Feedback label. 

@Reporter: Please follow steps mentioned in comment#1 and provide a trace file for further investigation from dev team.

Thanks!

Comment 4 by robliao@chromium.org, Apr 23 2018

Status: WontFix (was: Unconfirmed)
Closed due to inactivity. If we can get a repro for this issue without extensions, please reopen. Thanks!

Comment 5 by off...@mikemitterer.at, Apr 25 2018 

Sorry, here is the trace...
trace_Issu827788.json.gz
7.0 MB Download

Comment 6 by woxxom@gmail.com, Apr 25 2018 

The trace shows 100% of browser process time is spent in Surface::ActivateFrame.
It maxes out CPU for 100ms, then DisplayScheduler::SurfaceDamaged is invoked ~10 times at the end of the frame.
And this sequence repeats infinitely.

Looks similar to  issue 834421 .

Comment 7 by creis@chromium.org, Apr 30 2018

Cc: creis@chromium.org
Components: Internals>Services>Viz Internals>Sandbox>SiteIsolation
Mergedinto: 834421
Owner: sadrul@chromium.org
Status: Duplicate (was: WontFix)
Thanks for the update!  And indeed, this seems Site Isolation related since there's a subframe process in the screenshot of the original report.

sadrul@ landed a workaround for  issue 834421  in r554321 (68.0.3412.0), and we've just merged it to M67 for the upcoming beta build.  I'll mark this as a dupe of that bug, but let us know if you still see the problem in 68.0.3412.0 or later.
►

Sign in to add a comment