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

Issue 880499 link

Starred by 3 users
Status: Archived
Merged: issue 848210
Owner: ----
Closed: Nov 6
Cc:
█ krajshree@chromium.org
susan.boorgula@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Subframes may endlessly hog CPU resources in the background

Reported by lmi.itr....@gmail.com, Sep 4 
UserAgent: 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. Open various webpages containing twitter subframes
2. Check the Chrome task manager
3. You may see CPU usage stay stuck to 100%

What is the expected behavior?

What went wrong?
As an end user using Chrome heavily, I've opened a bunch of tabs, the CPU usage can be reasonable in most cases, that is until the process that contains series of "https://twitter.com/" subframes is launched and maxes out CPU Thread(s). I can temporarily remedy this by killing the process, but they may reappear over time or once I restart the browser.

I'm not sure whether this is a result of a website programming decision or an element in a subframe process that triggers Chrome to start an infinite loop inside of it, but either way I don't think Chrome should be allowing background subframes to indefinitely consume 100% CPU.

Did this work before? N/A 

Chrome version: 68.0.3440.106  Channel: stable
OS Version: 10.0
Flash Version:
twittersubframe maxed cpu.png
23.7 KB View Download

Comment 1 by dtapu...@chromium.org, Sep 4 

 Issue 880500  has been merged into this issue.

Comment 2 by phanindra.mandapaka@chromium.org, Sep 5

Labels: Needs-Milestone

Comment 3 Deleted

Comment 4 by susan.boorgula@chromium.org, Sep 5

Status: Unconfirmed (was: Duplicate)

Comment 5 by krajshree@chromium.org, Oct 11

Cc: krajshree@chromium.org
Components: Blink
Labels: Needs-Feedback
Unable to reproduce the issue on win-10 using chrome latest stable #69.0.3497.100. Observed that CPU usage did not reach even 20%.
Attached a screen shot for reference.
reporter@ - Could you please check the issue on latest stable #69.0.3497.100 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!
880499.PNG
78.8 KB View Download

Comment 6 by tkent@chromium.org, Nov 6

Status: Archived (was: Unconfirmed)
Feedback timeout
►

Sign in to add a comment