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

Issue 814439 link

Starred by 17 users
Status: Fixed
Owner:
chrishtr@chromium.org
Closed: Aug 7
Cc:
flackr@chromium.org
pdr@chromium.org
█ vollick@chromium.org
█ sindhu.chelamcherla@chromium.org
chaopeng@chromium.org
ajuma@chromium.org
enne@chromium.org
bokan@chromium.org
█ ranjitkan@chromium.org
chrishtr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

overflow: hidden causes excessive Update Layer Tree times due to compositing update

Project Member Reported by zjd@google.com, Feb 21 2018 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36

Steps to reproduce the problem:
With many overflow: hidden elements on the page, actions such as changing styles or scrolling become slow due to slow "Update Layer Tree" operations.

1. Open attached test case layer-overflow.html.
2. Click "Render".
3. Record performance timeline, move mouse around grid or scroll the page.
4. Observe excessive "Update Layer Tree" times.
5. Click "Toggle overflow: hidden" to remove overflow: hidden.
6. Repeat steps 3 & 4.
7. Notice that Update Layer Tree is now 600x faster (0.14 ms vs. 85.77 ms).

What is the expected behavior?
Update Layer Tree time with overflow: hidden should be comparable to Update Layer Tree time with overflow: visible.

What went wrong?
Update Layer Tree time with overflow: hidden was 600x slower than Update Layer Tree time with overflow: visible.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 64.0.3282.167  Channel: stable
OS Version: 4.9.0-5-amd64
Flash Version:
layer-overflow.html
1.7 KB View Download
update-layer-tree-overflow-visible.png
11.8 KB View Download
update-layer-tree-overflow-hidden.png
9.2 KB View Download

Comment 1 by schenney@chromium.org, Feb 26 2018

Mergedinto: 516437
Status: Duplicate (was: Unconfirmed)

Comment 2 by chrishtr@chromium.org, Mar 3 2018

Owner: chrishtr@chromium.org
Status: Assigned (was: Duplicate)

Comment 3 by chrishtr@chromium.org, Mar 3 2018

Summary: overflow: hidden causes excessive Update Layer Tree times due to compositing update (was: overflow: hidden causes excessive Update Layer Tree times)
Update: I have a prototype CL demonstrating a big improvement for this
example (which is common also).

https://chromium-review.googlesource.com/c/chromium/src/+/947578

Next up is to clean it up and commit it with tests.

Comment 4 by chrishtr@chromium.org, Mar 16 2018

Cc: chrishtr@chromium.org flackr@chromium.org bokan@chromium.org sindhu.chelamcherla@chromium.org ajuma@chromium.org
Issue 821071 has been merged into this issue.

Comment 5 by chrishtr@chromium.org, Mar 16 2018

Labels: allpublic

Comment 6 by bokan@chromium.org, Mar 21 2018

Cc: chaopeng@chromium.org
 Issue 823751  has been merged into this issue.

Comment 7 by chrishtr@chromium.org, May 2 2018

Cc: pdr@chromium.org enne@chromium.org ranjitkan@chromium.org vollick@chromium.org
 Issue 410867  has been merged into this issue.
Project Member

Comment 8 by bugdroid1@chromium.org, Jun 10 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/387c448f7c71cd902ad9d75a0447ba88a2adf461

commit 387c448f7c71cd902ad9d75a0447ba88a2adf461
Author: Chris Harrelson <chrishtr@chromium.org>
Date: Sun Jun 10 00:33:30 2018

Move CompositingReason::kClipsCompositingDescendants to its correct place.

The related FIXME was added in 2014 in this commit:

https://chromium.googlesource.com/chromium/src/+/c20dd68cff015b4c13969171c0f4e369ad8da06c

The overflow clip code has since been refactored to apparently remove the situation
mentioned there.

Bug:814439

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I5d7b777f125e4ac6e8bc46320bdce2f9c7c81878
Reviewed-on: https://chromium-review.googlesource.com/1087758
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565900}
[modify] https://crrev.com/387c448f7c71cd902ad9d75a0447ba88a2adf461/third_party/blink/renderer/core/dom/document.cc
[modify] https://crrev.com/387c448f7c71cd902ad9d75a0447ba88a2adf461/third_party/blink/renderer/core/paint/compositing/compositing_reason_finder.cc
[modify] https://crrev.com/387c448f7c71cd902ad9d75a0447ba88a2adf461/third_party/blink/renderer/core/paint/compositing/compositing_requirements_updater.cc
[modify] https://crrev.com/387c448f7c71cd902ad9d75a0447ba88a2adf461/third_party/blink/renderer/core/paint/paint_layer.cc
[modify] https://crrev.com/387c448f7c71cd902ad9d75a0447ba88a2adf461/third_party/blink/renderer/core/paint/paint_layer.h
[modify] https://crrev.com/387c448f7c71cd902ad9d75a0447ba88a2adf461/third_party/blink/renderer/core/style/computed_style.cc
[modify] https://crrev.com/387c448f7c71cd902ad9d75a0447ba88a2adf461/third_party/blink/renderer/core/style/computed_style.h
[modify] https://crrev.com/387c448f7c71cd902ad9d75a0447ba88a2adf461/third_party/blink/renderer/core/style/computed_style_test.cc
Project Member

Comment 9 by bugdroid1@chromium.org, Jun 11 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/38825770276009fd291931b3a8027102dd80a558

commit 38825770276009fd291931b3a8027102dd80a558
Author: Chris Harrelson <chrishtr@chromium.org>
Date: Mon Jun 11 04:33:52 2018

[PE] Rationalize compositing triggers.

* Compute all triggers except kComboSquashableReasons, kComboCompositedDescendants
and kComboAllCompositedScrollingDeterminedReasons in either style update or
CompositingInputsUpdater.
* Determine composited scrolling (but not the compositing trigger bit) in CompositingInputsUpdater.
* Cache these results on PaintLayer.

This achieves the following goals:
- Separates composited scrolling and awkward LCD text decisions from
the CompositingRequirementsUpdater step.
- Caches more triggers, leading to faster compositing updates in some cases
- Unblocks CL 1072155

Summary of implementation approach:

1. Dirty compositing inputs for all triggers computed there.
2. Compute, and cache on PaintLayer, kComboAllDirectNonStyleDeterminedReasons during
CompositingInputsUpdater.
3. Compute and cache a new DescendantHasDirectCompositingReason dirty bit on PaintLayer.
4. Update composited scrolling in PaintLayerScrollableArea during CompositingInputsUpdater.
This includes the root layer, which uses DescendantHasDirectCompositingReason as one of its
triggers.

Bug:814439,782991

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I21095762cbf806008395c2cf79f4ee038c39cb5f
Reviewed-on: https://chromium-review.googlesource.com/1087791
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565925}
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/animation/scroll_timeline.cc
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/html/html_frame_owner_element.cc
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/page/scrolling/root_scroller_controller.cc
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/paint/README.md
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/paint/compositing/compositing_inputs_updater.cc
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/paint/compositing/compositing_inputs_updater.h
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/paint/compositing/compositing_reason_finder.cc
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/paint/compositing/compositing_reason_finder.h
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/paint/compositing/compositing_reason_finder_test.cc
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/paint/compositing/compositing_requirements_updater.cc
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/paint/compositing/compositing_requirements_updater.h
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/paint/compositing/paint_layer_compositor.cc
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/paint/paint_layer.cc
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/core/paint/paint_layer.h
[modify] https://crrev.com/38825770276009fd291931b3a8027102dd80a558/third_party/blink/renderer/platform/graphics/compositing_reasons.h
Project Member

Comment 10 by bugdroid1@chromium.org, Jun 12 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/4a16d2254500b75f35f145bc79db56808aa02aa0

commit 4a16d2254500b75f35f145bc79db56808aa02aa0
Author: Chris Harrelson <chrishtr@chromium.org>
Date: Tue Jun 12 01:37:59 2018

Move kVideo direct compositing reason to CompositingReasonFinder::NonStyleDeterminedDirectReasons.

This is where it belongs.

Bug:814439

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Id0ac86deb9e4382e534b4ecea8d96f1313aadf89
Reviewed-on: https://chromium-review.googlesource.com/1093836
Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#566229}
[modify] https://crrev.com/4a16d2254500b75f35f145bc79db56808aa02aa0/third_party/blink/renderer/core/paint/compositing/compositing_reason_finder.cc
[modify] https://crrev.com/4a16d2254500b75f35f145bc79db56808aa02aa0/third_party/blink/renderer/core/paint/compositing/compositing_requirements_updater.cc
Project Member

Comment 11 by bugdroid1@chromium.org, Jun 13 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a3dfbb28e205cfc9d264b4ed4d0ccc7000a280bc

commit a3dfbb28e205cfc9d264b4ed4d0ccc7000a280bc
Author: Chris Harrelson <chrishtr@chromium.org>
Date: Wed Jun 13 21:40:51 2018

[CI] Don't compute "has composited ancestor scrolling layer" twice during requirements update.

Bug:  814439 
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ibf4b91b1a2486da71acf2286866ec999535af494
Reviewed-on: https://chromium-review.googlesource.com/1095816
Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#566999}
[modify] https://crrev.com/a3dfbb28e205cfc9d264b4ed4d0ccc7000a280bc/third_party/WebKit/LayoutTests/compositing/overflow/composited-scroll-overlap-test.html
[modify] https://crrev.com/a3dfbb28e205cfc9d264b4ed4d0ccc7000a280bc/third_party/blink/renderer/core/paint/compositing/compositing_requirements_updater.cc
Project Member

Comment 12 by bugdroid1@chromium.org, Jun 14 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2551aadf9bfc411f9f11e3894c4a5e7673da71a6

commit 2551aadf9bfc411f9f11e3894c4a5e7673da71a6
Author: Chris Harrelson <chrishtr@chromium.org>
Date: Thu Jun 14 05:42:05 2018

[PE] Refactor overlay controls reparenting to avoid the concept of a "topmost paint layer"

Previously, we computed which paint layer was topmost (but not negative z-index) in
CompositingLayerAssigner. This led to complications in invalidation, and makes it
hard to optimize that class to avoid recursions. Now compute the same thing through
smarter code in GraphicsLayerTreeBuilder and CompositingInputsUpdater.

Bug:814439

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I4c68e8622dde86be4870505696db6b453b4ab0e9
Reviewed-on: https://chromium-review.googlesource.com/1097559
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567157}
[modify] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/WebKit/LayoutTests/FlagExpectations/enable-slimming-paint-v2
[add] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/WebKit/LayoutTests/compositing/overflow/scrollbar-layer-placement-negative-z-index-child-expected.png
[add] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/WebKit/LayoutTests/compositing/overflow/scrollbar-layer-placement-negative-z-index-child-expected.txt
[add] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/WebKit/LayoutTests/compositing/overflow/scrollbar-layer-placement-negative-z-index-child.html
[modify] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/WebKit/LayoutTests/scrollbars/overlay-scrollbars-within-overflow-scroll.html
[modify] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/blink/renderer/core/frame/local_frame_view.cc
[modify] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/blink/renderer/core/frame/local_frame_view.h
[modify] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/blink/renderer/core/paint/compositing/composited_layer_mapping.cc
[modify] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/blink/renderer/core/paint/compositing/compositing_inputs_updater.cc
[modify] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/blink/renderer/core/paint/compositing/compositing_layer_assigner.cc
[modify] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/blink/renderer/core/paint/compositing/graphics_layer_tree_builder.cc
[modify] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/blink/renderer/core/paint/compositing/graphics_layer_tree_builder.h
[modify] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/blink/renderer/core/paint/compositing/paint_layer_compositor.cc
[modify] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/blink/renderer/core/paint/paint_layer_scrollable_area.cc
[modify] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/blink/renderer/core/paint/paint_layer_scrollable_area.h
[modify] https://crrev.com/2551aadf9bfc411f9f11e3894c4a5e7673da71a6/third_party/blink/renderer/platform/scroll/scrollable_area.h
Project Member

Comment 13 by bugdroid1@chromium.org, Jun 18 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/441691865aadd99164e8d23953ba15072e269587

commit 441691865aadd99164e8d23953ba15072e269587
Author: Chris Harrelson <chrishtr@chromium.org>
Date: Mon Jun 18 21:58:30 2018

[PE] Skip compositing requirements recursion when possible

All of these conditions must be true for the current PaintLayer:
1. The layer is not under a non-root composited scroller, or there are no
fixed/sticky descendants.
2. There are no non-contained absolute position descendants (i.e. ones whose containing
block skips the current layer).
3. The current layer has overflow clip.
4. There are no direct compositing reasons on any descendant.
5. There is no currently-composited descendant.

Bug:814439

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I74c1ad25ec1c5c20ec3629140b6555c89676a3ac
Reviewed-on: https://chromium-review.googlesource.com/1099972
Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Commit-Queue: Tien-Ren Chen <trchen@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568183}
[modify] https://crrev.com/441691865aadd99164e8d23953ba15072e269587/third_party/blink/renderer/core/paint/compositing/compositing_inputs_updater.cc
[modify] https://crrev.com/441691865aadd99164e8d23953ba15072e269587/third_party/blink/renderer/core/paint/compositing/compositing_requirements_updater.cc
[modify] https://crrev.com/441691865aadd99164e8d23953ba15072e269587/third_party/blink/renderer/core/paint/paint_layer.cc
[modify] https://crrev.com/441691865aadd99164e8d23953ba15072e269587/third_party/blink/renderer/core/paint/paint_layer.h
[modify] https://crrev.com/441691865aadd99164e8d23953ba15072e269587/third_party/blink/renderer/core/paint/paint_layer_test.cc
Project Member

Comment 14 by bugdroid1@chromium.org, Jun 26 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a9be49beca9893711aad3ffac2e00132d38c3bf8

commit a9be49beca9893711aad3ffac2e00132d38c3bf8
Author: Chris Harrelson <chrishtr@chromium.org>
Date: Tue Jun 26 03:30:11 2018

Optimize out work in CompositingLayerAssigner

* There is no need to do any work for a PaintLayer if it has no past/current compositing state.
* There is no need to recurse if the entire stacking subtree has no past/current compositing state.

Bug:  814439 

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ib1d2c23e1e2c9a34bea63432d95f83a8bbe0ab13
Reviewed-on: https://chromium-review.googlesource.com/1101817
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570321}
[modify] https://crrev.com/a9be49beca9893711aad3ffac2e00132d38c3bf8/third_party/blink/renderer/core/paint/compositing/composited_layer_mapping.cc
[modify] https://crrev.com/a9be49beca9893711aad3ffac2e00132d38c3bf8/third_party/blink/renderer/core/paint/compositing/compositing_layer_assigner.cc
[modify] https://crrev.com/a9be49beca9893711aad3ffac2e00132d38c3bf8/third_party/blink/renderer/core/paint/compositing/compositing_requirements_updater.cc
[modify] https://crrev.com/a9be49beca9893711aad3ffac2e00132d38c3bf8/third_party/blink/renderer/core/paint/paint_layer.cc
[modify] https://crrev.com/a9be49beca9893711aad3ffac2e00132d38c3bf8/third_party/blink/renderer/core/paint/paint_layer.h
Project Member

Comment 15 by bugdroid1@chromium.org, Aug 6 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/addacd4228de24dd9a61b98efed1f407649e1872

commit addacd4228de24dd9a61b98efed1f407649e1872
Author: Chris Harrelson <chrishtr@chromium.org>
Date: Mon Aug 06 20:14:17 2018

Account for border style when testing border width.

Previously, code in LayoutBox::StyleDidChange which
tried to detect change of border for clips did not
take into account changes of border style to hidden
or none.

Bug:  814439 

Change-Id: Ic59985c1b7b877cbbee678930328444d7700274e
Reviewed-on: https://chromium-review.googlesource.com/1163220
Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#580966}
[modify] https://crrev.com/addacd4228de24dd9a61b98efed1f407649e1872/third_party/blink/renderer/core/style/computed_style.h
[modify] https://crrev.com/addacd4228de24dd9a61b98efed1f407649e1872/third_party/blink/renderer/core/style/computed_style_test.cc
Project Member

Comment 16 by bugdroid1@chromium.org, Aug 6 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124

commit ba8c87a1a32815e6061b7c38d31ddfbbaac7a124
Author: Chris Harrelson <chrishtr@chromium.org>
Date: Mon Aug 06 22:24:31 2018

Only invalidate property trees and compositing for PaintLayers when needed, on style change.

Previously we unconditionally invalidated both on any style change.

Most of the changes in this patch are updates of code that looks like:

SetNeedsPaintPropertyUpdate();

to:

SetNeedsPaintPropertyUpdate();
if (Layer())
  Layer()->SetNeedsCompositingInputsUpdate();

in cases where the LayoutObject in question might have a PaintLayer. The call to
SetNeedsCompositingInputsUpdate() cannot be pushed down into SetNeedsPaintPropertyUpdate()
because SetNeedsPaintPropertyUpdate() is called from SPv1 compositing code post-inputs, and
it's illegal to set lifecycle bits for that phase after it has already completed.

Bug:  814439 
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I8c2aa3d451ad24e6feb0b14858bdba09d42f4ef5
Reviewed-on: https://chromium-review.googlesource.com/1157651
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581008}
[modify] https://crrev.com/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124/third_party/blink/renderer/core/layout/layout_block.cc
[modify] https://crrev.com/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124/third_party/blink/renderer/core/layout/layout_box.cc
[modify] https://crrev.com/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124/third_party/blink/renderer/core/layout/layout_box_model_object.cc
[modify] https://crrev.com/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124/third_party/blink/renderer/core/layout/layout_menu_list.cc
[modify] https://crrev.com/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124/third_party/blink/renderer/core/layout/layout_object.cc
[modify] https://crrev.com/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124/third_party/blink/renderer/core/layout/layout_replaced.cc
[modify] https://crrev.com/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124/third_party/blink/renderer/core/layout/layout_view.cc
[modify] https://crrev.com/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124/third_party/blink/renderer/core/layout/svg/layout_svg_foreign_object.cc
[modify] https://crrev.com/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124/third_party/blink/renderer/core/layout/svg/layout_svg_root.cc
[modify] https://crrev.com/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124/third_party/blink/renderer/core/paint/paint_layer.cc
[modify] https://crrev.com/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124/third_party/blink/renderer/core/paint/paint_layer_scrollable_area_test.cc

Comment 17 by chrishtr@chromium.org, Aug 7

Status: Fixed (was: Assigned)
Frame rates in the example in #0 are now very low.
►

Sign in to add a comment