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

Issue 645496 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Sep 2016
Cc:
█ vollick@chromium.org
majidvp@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Extreme lag on complex CompositorWorker parallax page

Project Member Reported by flackr@chromium.org, Sep 9 2016 
Version: 55.0.2855.0 (Developer Build) (64-bit)
OS: Linux

What steps will reproduce the problem?
(1) Compare scrolling the attached test page with http://flackr.github.io/compositor-worker/parallax-static/parallax.html with --enable-blink-features=GeometryInterfaces,CompositorWorker

What is the expected output?
The green box should stick to the top of the document reasonably well in both. 

What do you see instead?
In test-overflow.html the green box sticks reasonably well (other than the jitter issue described in issue 585458) but on the parallax demo there is extreme jank and the framerate is very low.

I've tried tracing it but I don't see anything that's obviously wrong at a glance.

Please use labels and text to provide additional information.
test-overflow.html
1.2 KB View Download

Comment 1 by flackr@chromium.org, Sep 12 2016

Summary: Extreme lag on complex CompositorWorker parallax page (was: Extreme jank on complex CompositorWorker parallax page)
We found out the difference between content shell and chrome was caused by the GPU blacklist, there were extremely long frame times in the browser process. Running with --ignore-gpu-blacklist chrome behaved the same as content shell.

This fixes the jank but the content is still way behind.

The content moves correctly if we run without scroll animations - i.e. with the --disable-smooth-scrolling flag.

Comment 2 by flackr@chromium.org, Sep 12 2016

Status: WontFix (was: Untriaged)
We figured out the issue, we were running the compositor worker code again after the commit but it was trying not to do work if nothing had changed and so it thought it had already handled that scroll update.
►

Sign in to add a comment