1303815 - Slow Painting & checkerboard effect on www.breitbart.com

Status: RESOLVED DUPLICATE of bug 1256677

(Core :: Graphics, defect)

Description

[bull500]

Attachment: checkerboard.mp4

Visit http://www.breitbart.com/big-government/2016/09/19/police-capture-ahmad-khan-rahami-suspect-ny-nj-bombings/   

51.0a1 (2016-09-19) (64-bit)

Scroll down fast with mouse wheel to notice the slow painting checkerboard effect effect; Video attached

Comment 1

[Lee Salzman [:lsalzman]]

Could you attach the Graphics section of about:support?

Also, if you are able, could you run mozregression (http://mozilla.github.io/mozregression/) to determine what version and more specifically if possible what revision this issue started with?

Comment 2

[bull500]

(In reply to Lee Salzman [:lsalzman] from comment #1)
> Could you attach the Graphics section of about:support?
> 
> Also, if you are able, could you run mozregression
> (http://mozilla.github.io/mozregression/) to determine what version and more
> specifically if possible what revision this issue started with?

Graphics
Features
Compositing	OpenGL
Asynchronous Pan/Zoom	wheel input enabled; touch input enabled
WebGL Renderer	Intel Open Source Technology Center -- Mesa DRI Intel(R) Sandybridge Mobile
WebGL2 Renderer	WebGL creation failed: * WebGL 2 requires support for the following features: transform_feedback2 * Exhausted GL driver options.
Hardware H264 Decoding	No
Audio Backend	pulse
GPU #1
Active	Yes
Description	Intel Open Source Technology Center -- Mesa DRI Intel(R) Sandybridge Mobile
Vendor ID	Intel Open Source Technology Center
Device ID	Mesa DRI Intel(R) Sandybridge Mobile
Driver Version	3.0 Mesa 10.6.9 (git-8957b69)
Diagnostics
AzureCanvasAccelerated	0
AzureCanvasBackend	skia
AzureContentBackend	skia
AzureFallbackCanvasBackend	none
CairoUseXRender	0
failures	[GFX1-]: Refresh driver waiting for the compositor for 2.27976 seconds.
Failure Log
(#0) Error	Refresh driver waiting for the compositor for 2.27976 seconds.
(#1) 	CP+[GFX1-]: Refresh driver waiting for the compositor for 11.006 seconds.    



Had a hard time with mozregression before :/   
Ill try again and if i can make it work ill post back on it
I just noticed this out of the blue. It was my first visit to the site and happened to notice it.

Comment 3

[Lee Salzman [:lsalzman]]

If you toggle the layers.acceleration.disabled pref to true, and make sure layers.acceleration.force-enabled is false, does the problem go away?

This could be related to our experiment with enabling GL layers on Nightly builds, if that is what you are using.

Comment 4

[bull500]

(In reply to Lee Salzman [:lsalzman] from comment #3)
> If you toggle the layers.acceleration.disabled pref to true, and make sure
> layers.acceleration.force-enabled is false, does the problem go away?
> 
> This could be related to our experiment with enabling GL layers on Nightly
> builds, if that is what you are using.

Sorry but it still happens even after doing the above steps. :(  
Its a bit harder - as you need to mouse scroll a tiny bit faster than before

Comment 5

[roxleitan]

Regression range:

Last good revision: 077a6b1a1ba5abd927990e01740806c76f899f9b 

First bad revision: 30742281c223e2a7abb5931ee5383d890b5ce0e8

Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=077a6b1a1ba5abd927990e01740806c76f899f9b&tochange=30742281c223e2a7abb5931ee5383d890b5ce0e8

Looks like the following bug has the changes which introduced the regression:
Bug 1143856

Comment 6

[Kartikaya Gupta (email:[e-mail])]

Checkerboarding, particularly during page load when a lot of scripts are running, is basically unavoidable with APZ. We have a bug on file to track possible improvements.