google io 2015 site has janky animations in firefox

NEW
Unassigned

Status

()

Core
Graphics
3 years ago
2 years ago

People

(Reporter: bkelly, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: gfx-noted)

(Reporter)

Description

3 years ago
Open the new google IO site for 2015:

  https://events.google.com/io2015/

Click on the "Learn more about I/O" to go to:

  https://events.google.com/io2015/about

Observe animation jank.  Here is a profile where did this a couple times:

  http://people.mozilla.org/~bgirard/cleopatra/#report=ff1340155897196d126bbfaf89288b804a89c43e

Putting this in gfx because the profile shows some massive rasterize blocks.

Note, the large script blocks are probably where they are doing their "FLIP" technique described here:

  http://aerotwist.com/blog/flip-your-animations/
(Reporter)

Comment 1

3 years ago
Any thoughts on the profile in comment 0?
Flags: needinfo?(bgirard)
(Reporter)

Comment 2

3 years ago
Multiple long (60ms+) instances where we are stuck on NtGdiDdDDILock in the windows gfx libs.  Maybe this is more a question for Bas.

I'm on windows 8.1.  Here's my graphics hardware info:

Adapter Description	NVIDIA Quadro 600
Adapter Drivers	nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM	1024
Device ID	0x0df8
Direct2D Enabled	true
DirectWrite Enabled	true (6.3.9600.17111)
Driver Date	8-29-2013
Driver Version	9.18.13.2702
GPU #2 Active	false
GPU Accelerated Windows	1/1 Direct3D 11 (OMTC)
Subsys ID	083510de
Vendor ID	0x10de
WebGL Renderer	Google Inc. -- ANGLE (NVIDIA Quadro 600 Direct3D11 vs_5_0 ps_5_0)
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d 1.1
AzureContentBackend	direct2d 1.1
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0
Flags: needinfo?(bgirard) → needinfo?(bas)
We're spending a noticeable amount of time in RenderLayerWithReadback. That doesn't seem good.
Whiteboard: gfx-noted
Is this still happening and/or do we still care?
Flags: needinfo?(bas)
You need to log in before you can comment on or make changes to this bug.