998754 - Higher GPU- and CPU-load and jerky scrolling on im.qq.com

Status: RESOLVED DUPLICATE of bug 996226

(Core :: Graphics, defect)

Description

[Elbart]

STR:
Open URL and maximize the window.
Scroll down with the mousewheel (it's possible even if there's no scrollbar)

ER:
GPU- and CPU-load as before the regression-range, rather smooth animations and scrolling.

AR:
High GPU- and CPU-load, scrolling and animations are jerky and visibly stuttering.

----------------

about:support:

--------
gfx.direct3d.last_used_feature_level_idx: 0

Graphics
--------

Adapter Description: NVIDIA GeForce GT 640
Adapter Drivers: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM: 2048
ClearType Parameters: Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 300
Device ID: 0x0fc1
Direct2D Enabled: true
DirectWrite Enabled: true (6.2.9200.16571)
Driver Date: 6-21-2013
Driver Version: 9.18.13.2049
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 10
Vendor ID: 0x10de
WebGL Renderer: Google Inc. -- ANGLE (NVIDIA GeForce GT 640 Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote: false
AzureCanvasBackend: direct2d
AzureContentBackend: direct2d
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0


----------------


Regression window:
m-c:
Last good revision: b0e7f63c2138 (2014-03-07)
First bad revision: d01bf8596d3b (2014-03-08)
Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b0e7f63c2138&tochange=d01bf8596d3b

m-i:
Last good revision: 9fafd0e46813
First bad revision: 69cb6eddfc77
Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=9fafd0e46813&tochange=69cb6eddfc77

Comment 1

[Elbart]

Attachment: Comparison of CPU- and GPU-load

Comment 2

[Elbart]

Bisecting m-c:
===
$ hg bisect -b
The first bad revision is:
←[0;33mchangeset:   172610:a3bf4be14ce0←[0m
parent:      172609:f952ac387d75
parent:      172590:cd67334b34c5
user:        Ryan VanderMeulen <[e-mail]>
date:        Fri Mar 07 15:45:57 2014 -0500
summary:     Merge m-c to inbound.

Not all ancestors of this changeset have been checked.
Use bisect --extend to continue the bisection from
the common ancestor, c9f09336bc6c.
===
https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=a3bf4be14ce0

Bisecting m-i
===
The first bad revision is:
←[0;33mchangeset:   172599:a3bf4be14ce0←[0m
parent:      172540:f952ac387d75
parent:      172598:cd67334b34c5
user:        Ryan VanderMeulen <[e-mail]>
date:        Fri Mar 07 15:45:57 2014 -0500
summary:     Merge m-c to inbound.

Not all ancestors of this changeset have been checked.
Use bisect --extend to continue the bisection from
the common ancestor, c9f09336bc6c.
===
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?changeset=a3bf4be14ce0


Maybe bug 962670?

Comment 3

[Milan Sreckovic [:milan] (needinfo for best results)]

I believe Michael is backing out the volatile buffers change on most platforms.

Comment 4

[Michael Wu [:mwu]]

Not backed out, but disabled. See bug 996226 .

Comment 5

[Elbart]

Yes, CPU- and GPU-load are back to "normal" in Nighty 2014-04-23.

Comment 6

[Wayne Mery (:wsmwk)]

(In reply to Elbart from comment #5)
> Yes, CPU- and GPU-load are back to "normal" in Nighty 2014-04-23.

so this is a dup?  (having trouble figuring out which bug, assuming there is intention to reenable on non-B2G)

Comment 7

[Milan Sreckovic [:milan] (needinfo for best results)]

Right, ends up being fixed by patches on bug 996226.