1254206 - Graphic Artifacts on about:support

Status: RESOLVED DUPLICATE of bug 1261483

(Core :: Widget: Cocoa, defect, P1)

Description

[Mason Chang [Inactive] [:mchang]]

Attachment: Screen Shot 2016-03-07 at 10.34.50 AM.png

STR:

1) go to about:support
2) See screenshot

This seemed to break over the weekend

Comment 1

[Mason Chang [Inactive] [:mchang]]

[Tracking Requested - why for this release]: Pretty bad graphics artifacts.

Comment 2

[Mason Chang [Inactive] [:mchang]]

Attachment: Another screenshot

Another screenshot with the bug. I tried disabling APZ and that didn't seem to matter.

Comment 3

[Mason Chang [Inactive] [:mchang]]

BTW, this was tested on a late 2013 retina macbook pro 15".

Comment 4

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

So far, yours is the only computer exhibiting this?  I haven't seen this problem on my 10.11 early 2013 retina 15".

Comment 5

[Mason Chang [Inactive] [:mchang]]

(In reply to Milan Sreckovic [:milan] from comment #4)
> So far, yours is the only computer exhibiting this?  I haven't seen this
> problem on my 10.11 early 2013 retina 15".

So far it looks like it. Matt also has a late retina 2013 and it doesn't exhibit it. I loaded gfxCardStatus which lets you choose an explicit GPU. If I explicitly pick only the nvidia or only the intel card, i can't reproduce the problem. The problem seems to happen only if the gpu change occurs during loading about:support.

This only started happening this week, and never before. I tried finding a regression range, but I could even reproduce the problem way back in Release on Gecko 45. I wonder if this is just the hardware randomly failing as I've never actually had this problem while visiting sites.

Comment 6

[Cosmin Muntean [:cmuntean], Ecosystem QA]

Firefox: 45.0 Build ID: 20160303134406
User Agent  Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:48.0) Gecko/20100101 Firefox/48.0

Hi Mason,

I have tested this issue on the latest Firefox (45.0) release, latest Nightly (48.0a1 - 20160308030418 ) build and I could not reproduce it. I have tested on a retina MAC book pro 13" and the "about:support" page is correctly loaded. Is the "about:support" the only page where the bug appear? 

Can you please test this on the latest Firefox release or latest Nightly build (https://nightly.mozilla.org/) and report back the results ? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E). 

Thanks,
Cosmin.

Comment 7

[Mason Chang [Inactive] [:mchang]]

(In reply to Cosmin Muntean [:CosminMCG] from comment #6)
> Firefox: 45.0 Build ID: 20160303134406
> User Agent  Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:48.0)
> Gecko/20100101 Firefox/48.0
> 
> Hi Mason,
> 
> I have tested this issue on the latest Firefox (45.0) release, latest
> Nightly (48.0a1 - 20160308030418 ) build and I could not reproduce it. I
> have tested on a retina MAC book pro 13" and the "about:support" page is
> correctly loaded. Is the "about:support" the only page where the bug appear? 

Yes, you may have to reload about:support 4-5 times after closing and reloading firefox to appear. I was able to reproduce this on the latest nightly and release. I cannot reproduce this on a late 2013 iMac as well. I've asked around on irc and nobody else can reproduce this also.

> 
> Can you please test this on the latest Firefox release or latest Nightly
> build (https://nightly.mozilla.org/) and report back the results ? When
> doing this, please use a new clean Firefox profile, maybe even safe mode, to
> eliminate custom settings as a possible cause (https://goo.gl/PNe90E). 
> 

I tried a new profile but that didn't solve the issue. Safe mode / disabling acceleration fixes the problem.

> Thanks,
> Cosmin.

Comment 8

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

I think you broke your computer :)

Comment 9

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

Tracked for Fx 47 based on the visual artifacts in the screen shot. If we are not able to find a consistent or widespread repro, we may decide to untrack.

Comment 10

[Mason Chang [Inactive] [:mchang]]

(In reply to Ritu Kothari (:ritu) from comment #9)
> Tracked for Fx 47 based on the visual artifacts in the screen shot. If we
> are not able to find a consistent or widespread repro, we may decide to
> untrack.

I think we should untrack. I just got visual artifacts in OS X mail that were similar to this, so I think it's comment 8, my computer.

Comment 11

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

(In reply to Mason Chang [:mchang] from comment #10)
> (In reply to Ritu Kothari (:ritu) from comment #9)
> > Tracked for Fx 47 based on the visual artifacts in the screen shot. If we
> > are not able to find a consistent or widespread repro, we may decide to
> > untrack.
> 
> I think we should untrack. I just got visual artifacts in OS X mail that
> were similar to this, so I think it's comment 8, my computer.

Ok, untracked.