New issue
Advanced search Search tips

Issue 601634 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Throttle rendering of detached FrameViews

Project Member Reported by wangxianzhu@chromium.org, Apr 7 2016

Issue description

Detached frames are frames whose owner node (<frame> or <iframe>) has display:none or other styles making the owner node not rendered.

For now we update almost the whole document cycle for detached FrameViews.

Can we use the frame throttling mechanism for detached FrameViews?

We also refer FrameViews with null layoutView() as detached. However, I see the detached FrameViews have null frame().ownerLayoutObject() but non-null layoutView(). What's the case of null layoutView()?


 
Seems like a good idea. Do you have an idea of how common detached FrameViews are?
Saw some layout tests and unit tests testing <iframe style="display: none">. Will run a cluster-telemetry task to see how common they are in 10k sites.
Components: -Blink Blink>Scheduling
https://ct.skia.org/chromium_perf_runs/ run 736
For desktop top 10k sites:

Total number of frames: 38963
Number of throttled frames: 13622
Number of detached frames: 14823
Number of detached frames that are also throttled: 4661

Based on this data, throttling detached frames will benefit us.

Besides performance, we'll also simplify some code handling detached frames, e.g. FrameView::invalidateTreeIfNeededRecursive(). 
Thanks for putting the data together. Seems like an even better idea now :)
Project Member

Comment 6 by sheriffbot@chromium.org, Apr 11 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue.
The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Note that we accidentally shipped throttling display:none frames in M56 (I think) and had to roll back because it broke some sites.
Owner: skyos...@chromium.org
Status: WontFix (was: Untriaged)
I believe that we can't throttle display:none frames because it will cause major breakage. Sami, am I right? If not, please reopen the bug.
That's right, although there's some ongoing spec work to allow that which should ultimately let us do this.

Sign in to add a comment