1241157 - Glitchy imgur decode (4k scaled down images)

Status: RESOLVED INVALID

(Core :: Graphics, defect)

Description

[Benoit Girard (:BenWa)]

STR:
0) Performing the following from a *fresh* private browsing window to have fresh caches.
1) Load http://imgur.com/a/pUMFP
2) Scroll up and down quickly
3) Notice rendering artifacts

Comment 1

[Timothy Nikkel (:tnikkel)]

Not sure if I can see this or not, it all happens so fast. What kind of artifacts do you see?

Comment 2

[Benoit Girard (:BenWa)]

Attachment: decodebug.gif

Here's an example. GIF is low frame rate so it's a bit harder to see. At some point you see something like 7 overlapping copies of the image frame borders.

Some of the ugly I think is just APZ background color checkerboard but I think the overlapping copies is not intentional glitching.

Comment 3

[Paul Pasca[Away. Please needinfo? Paul Oiegas [:pauloiegasSV]]]

Hi Benoit,

I haven't managed to reproduce this issue on the latest release(44.0) nor latest Nightly(47.0a1). Scrolling up and down really fast is not causing any graphics problems as seen in your GIF.

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20160123151951

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID: 20160127030236

Can you please provide what version of Firefox caused this? An in what OS this issue occurred? It will help a lot if this needs a regression.

Also, please try to reproduce this on the latest release(44.0) and latest Nightly(47.0a1) and provide the results. When doing this, please try to reproduce with a new clean Firefox profile, maybe even in safe mode, as some of this issues may be caused by third party installed add-ons or custom settings(https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems).

Thanks,
Paul.

Comment 4

[Benoit Girard (:BenWa)]

I can still reproduce it on 47.0a1 (2016-01-30) using OSX 10.11.

Comment 5

[Benoit Girard (:BenWa)]

I tried bisecting but it wasn't very productive. I'm just going to write this off as a checkerboarding bug.