User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0 Build ID: 20121023124120 Steps to reproduce: Opened the attached testcase in Firefox 17 beta 3. Scrolled to the bottom of the page, then scrolled up and down the page repeatedly by dragging the scrollbar. Actual results: When reaching the very top of the page, intermittently the display of the page content will become garbled. Expected results: The page should display normally after scrolling. I have been unable to reproduce the problem with Direct2D disabled, or in Firefox 16.0.2 or 19 Nightly. Graphics information from about:support Graphics Adapter Description NVIDIA GeForce 210 Vendor ID 0x10de Device ID 0x0a65 Adapter RAM 512 Adapter Drivers nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um Driver Version 9.18.13.697 Driver Date 10-2-2012 Direct2D Enabled true DirectWrite Enabled true (6.1.7601.17789) ClearType Parameters ClearType parameters not found WebGL Renderer Google Inc. -- ANGLE (NVIDIA GeForce 210 ) -- OpenGL ES 2.0 (ANGLE 1.0.0.1242) GPU Accelerated Windows 1/1 Direct3D 10 AzureCanvasBackend direct2d AzureFallbackCanvasBackend cairo AzureContentBackend direct2d

most likely Bug 782311

If you see artifacts use shortcut CTRL+A for "Select All". If artifacts will be gone, this bug is most likely a duplicate of bug 782311

I can reproduce this reliably on OS X, so I doubt it's an exact duplicate of a D3D bug. http://howtosharpenpencils.tumblr.com/post/35285338188/the-peoples-bailout is another testcase.

I see this on Reddit too. See attachment 680415 [details] for a screenshot of what I get on http://www.reddit.com/r/shutupandtakemymoney/ It basically makes Firefox unusable on such sites. Was this DLBI fallout? Seems like it's started more recently, at least for this Reddit issue.

I can no longer reproduce this bug on recent nightlies -- is it fixed?

I can't reproduce it either, would it be possible to get a regression range for when it was fixed?

Maybe with fixed bug #782311 ?

I previously saw this, and like the original reporter have an nVidia card. (2010 MBA.) How would I go about testing the builds before/after that fix was committed?

Looking on regression range in my bug #782311 : Good: https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2012/07/2012-07-25-03-05-56-mozilla-central/ Bad: https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2012/07/2012-07-26-05-28-03-mozilla-central/

The test case was still broken in the 11-10 build: https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2012/11/2012-11-10-03-07-14-mozilla-central/ But works for me in the 11-11 build: https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2012/11/2012-11-11-03-07-49-mozilla-central/ I think that's consistent with Bug 782311 fixing this issue?

Looking on commit date, yep. But lets wait on info from Reuben Morais [:reuben] as he also see it's even on OS X

(In reply to Virtual_ManPL [:Virtual] from comment #12) Nope, I haven't seen this bug in a while.

So we can close this bug as dupe of my bug #782311 or mark it as WORKSFORME.

Guys which could confirm this issue, I need some more info about your PC specification. Especially: -motherboard and chipset info -GPU working on which PCIe (3.0/2.1/2.0/1.1/1.0) -monitor info (type, resolution, refresh rate, connected with HDMI/DVI/DisplayPort/VGA CPU/memory/sound card/PSU/etc is optional Thank you!

Here's a report from CPU-Z, hopefully it has all the required information - please let me know if not. There are two Samsung SyncMaster 740T displays attached using DVI, one of them is using a HDMI-to-DVI cable.