User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 Build ID: 20160315153207 Steps to reproduce: I've browsed to http://business-programming.com/business_programming.html#section-17 and then started scrolling the page to continue reading from that point. Actual results: The main contents of the page often does not scroll, and only a small stripe (a few pixels high) at the top of the page does scroll. I've tested it on at least 2 computers: 1) Windows 10; Fx 45.0.1; GPU is Intel HD 515. 2) Windows 10; Fx 44.0.2; dual GPU, Intel HD 4600 is the base one. No plugins. On (1), after I disabled GPU acceleration & smooth scrolling, the effect seems much less pronounced (see the attached video). I'll try to submit a video done with normal settings later too; it is much worse (that's why I disabled the acceleration), makes it impossible to read the page. Expected results: Full page contents should be scrolling properly.

Sorry wrong bug.

the movie recording I made proved too big for attachment, so I've put it on Dropbox at: https://www.dropbox.com/s/2sahoybwzi9863v/tearing.mp4?dl=0

Fixed in Nightly by bug 1209100: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=6b034852b39fb66515bd80027ee5ab688a9ed60f&tochange=4c254ac91a0e4a99d75c6ab90a3e8ce4853aa925

@Alice0775, is your "Fixed in Nightly" comment again "Sorry wrong bug"? Or is it this time meant to refer to the bug I reported? TIA

Appearances of this bug is different that reported in bug 1209100. So, I cannot say that this is exactly duplication of bug 1209100.

I've uploaded the second video on Drop box at: https://www.dropbox.com/s/zr6ypz73dvkygok/strong%20tearing.mp4?dl=0 It shows behavior with GPU acceleration & smooth scrolling enabled back.

Oook; so I've downloaded the 48 Nightly, and my issue seems indeed not to show up anymore too! I've only tested for a short while, but it looked much more stable, didn't see any hints of the bad behavior, while on current they show up quite fast. So, from my side, I suppose you can mark it resolved in 48 or something. Thanks, that was fast! ;)

Hmm, may not be an exact duplicate but maybe it was fixed by the backout in 1209100? Markus do you think so?

Too late for a fix for beta 46. We could still potentially uplift to 47.

As per comment 4, this issue is fixed by bug 1209100. Updating status Fx47 to reflect that.

Yes, this was fixed by the backout in bug 1209100.