New issue
Advanced search Search tips

Issue 763579 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

consider throttling offscreen same-origin frames

Project Member Reported by ojan@chromium.org, Sep 8 2017

Issue description

It turns out a large percentage of ads are in same origin frames. I think it's less reasonable as a platform to throttle same origin frames since malicious code can easily bypass it. But the vast majority of CPU problems from ads are accidental, not malicious.

One thing we could consider is throttling only same origin frames that are in the scrollable region. That way we don't throttle iframes used as transport, which are typically absolutely positioned above or to the left of the page's scrollable region, so there's no way for the user to get to it.
 
Owner: altimin@chromium.org
Status: Assigned (was: Available)
We discussed this briefly. Let's try shipping this without any special logic that differs from cross-origin frames first. If that doesn't work we can come up with something more elaborate.
Labels: -Pri-2 Pri-3
The initial data suggests that there are better things to focus our efforts on. Lowering priority to P3, will revisit when data from stable comes.
Labels: -Type-Bug Type-Feature

Sign in to add a comment