1139430 - Images are corrupt or black on Windows 8.1

Status: RESOLVED DUPLICATE of bug 1138061

(Core :: Graphics, defect)

Description

[Hilltop]

Attachment: screenshot1.PNG

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150222232811

Steps to reproduce:

Visit any website which has JPG images displayed.  For example, my screenshot shows www.spiceworks.com/free-help-desk-software/ but this happens on any site utilizing jpeg images.  Does not appear to be occurring with PNG or other formats.  YouTube also shows the problem.

I have disabled all plugins (only had Flash and the stock extensions included in Firefox anyway).

Not running any third party firewall or web filtering software.

Not running through a proxy.

Windows 8.1 x64

Persists over reboots and firefox relaunches.


Actual results:

JPEG images display with black areas, black bars, or as black squares with no image visible.

Refreshing the page may or may not correct the image.  Usually if retrieving the image again (not using cached image) the image works fine.


Expected results:

JPEG files should displayed properly.

Comment 1

[Matthias Versen [:Matti]]

Please disable the graphic hardware acceleration in Firefox:options/advanced/general and restart Firefox.
In case that the issue is now gone, open about:support (enter as URL) and copy the graphic section of that page and paste it in this bug as comment.

Comment 2

[Hilltop]

I disabled hardware acceleration and now I am seeing corrupted JPEGs with *white* missing areas, instead of black areas.  See attachment.  Refreshing until it stops loading existing cached image and retrieves the original again corrects the image.

Comment 3

[Hilltop]

Sorry, I made a mistake.  The ones corrupted this time in the example attachment were PNG files.

Comment 4

[Hilltop]

Attachment: Corrupted PNGs after disabling hardware acceleration

Comment 5

[Chad Douglas]

Attachment: Image Corruption

I'm seeing this too (version 36.0.1). It's not on every page though. I disabled hardware acceleration and didn't see it (or notice any other issues). The problem is intermittent though. My graphics information is as follows.

Adapter Description	NVIDIA GeForce GTX 260
Adapter Drivers	nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM	896
Device ID	0x05e2
Direct2D Enabled	true
DirectWrite Enabled	true (6.3.9600.17415)
Driver Date	2-3-2015
Driver Version	9.18.13.4144
GPU #2 Active	false
GPU Accelerated Windows	7/7 Direct3D 11 (OMTC)
Subsys ID	12653842
Vendor ID	0x10de
WebGL Renderer	Google Inc. -- ANGLE (NVIDIA GeForce GTX 260 Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d
AzureContentBackend	direct2d
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0

Comment 6

[Chad Douglas]

I should add my user agent:

Mozilla/5.0 (Windows NT 6.3; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0

Comment 7

[thefreshmaker2]

Same here!

Windows 8.1

Firefox 36.0.1 

This happened immediately after update.

Most images on the page get corrupted after some tab switching.

Comment 8

[Seth Fowler [:seth] [:s2h]]

Bas, this really smells like graphics or layers to me. Especially since everyone reporting this is on Windows 8.1. I suspect you may have a better idea of where to start looking than I do.

Comment 9

[Bas Schouten (:bas.schouten)]

(In reply to Seth Fowler [:seth] from comment #8)
> Bas, this really smells like graphics or layers to me. Especially since
> everyone reporting this is on Windows 8.1. I suspect you may have a better
> idea of where to start looking than I do.

I have absolutely no idea, we should get affected hardware I suppose. It smells fishy though, since this started after 36.0.1... what changed in 36.0.1?

Comment 10

[Chad Douglas]

(In reply to Bas Schouten (:bas.schouten) from comment #9)
> I have absolutely no idea, we should get affected hardware I suppose. It
> smells fishy though, since this started after 36.0.1... what changed in
> 36.0.1?

The issue was present in 36.0.

Comment 11

[Seth Fowler [:seth] [:s2h]]

I have no idea what's going on here.

Timothy had a good suggestion: we could make some try builds that have various features disabled to see whether those eliminate the problem.

I wonder in particular if disabling layerization of images will make the problem go away.

Comment 12

[Seth Fowler [:seth] [:s2h]]

Hilltop, I'm curious about one thing: if you set the pref "image.mem.surfacecache.min_expiration_ms" to 3600000 in about:config, and then restart the browser, do you still see the problem? (Or more accurately, do you still see the problem in pages that have been open for less than an hour?)

Comment 13

[Chad Douglas]

(In reply to Seth Fowler [:seth] from comment #12)
> Hilltop, I'm curious about one thing: if you set the pref
> "image.mem.surfacecache.min_expiration_ms" to 3600000 in about:config, and
> then restart the browser, do you still see the problem? (Or more accurately,
> do you still see the problem in pages that have been open for less than an
> hour?)

I set that pref yesterday and I'm still getting corruption in freshly loaded pages in new windows. FF has been running for 26 hours at this point and the issue and only got bad relatively recently. I have a lot of tabs open (about 75) and the browser's using 2GB of RAM so this is usually when it crashes.

Comment 14

[Chad Douglas]

Attachment: Page redraw errors

As I was posting the last comment I started getting weird page redraw issues. I don't know if it's relevant to the bug, but it's time for me to reset the pref and restart. (And maybe buy a new graphics card.)

Comment 15

[thefreshmaker2]

Turning off Hardware Acceleration seems to fix the problem. Both of our workstations have stopped producing the bug. Now the problem is that sometimes the browser won't switch tabs, until you click between the tabs a couple of times.

Comment 17

[Robert (rrayborn, he/him)]

Just chiming in from the user feedback side of things.  It looks like there is an increase in reports of black images in 36.0.  I think that this is an issue in Core since it's present in both Desktop and Android feedback:

Desktop: https://input.mozilla.org/en-US/?product=Firefox&date_start=2014-12-24&selected=90d&q=black+%2B+image&happy=0
Android: https://input.mozilla.org/en-US/?date_start=2014-12-24&selected=90d&q=black+%2B+image&happy=0&product=Firefox%20for%20Android

I'm looking through the feedback now, will update if I find anything specific.

Thanks

Comment 18

[Robert (rrayborn, he/him)]

Looks like I chimed in too soon; it appears that the issue on Android is separate bug and has been fixed in Firefox for Android 37.

Thanks

Comment 19

[spizzbool]

Disabling hardware acceleration works for me. Win 8.1 x64, GeForce GTX 560, driver version 347.52.

Comment 20

[Seth Fowler [:seth] [:s2h]]

At this point, given that turning off hardware acceleration fixes the issue and that comment 13 suggests that image discarding is not the problem, I think this is probably a graphics issue. I'm going to move it to the Graphics component to make sure that the right people see it.

Comment 21

[Timothy Nikkel (:tnikkel)]

Can anyone reproduce this easily enough to bisect? Doesn't seem like we are making much progress here, maybe knowing what broke this might help with that.

Comment 22

[dusty-2011]

The original bug that Hilltop posted here in the user story was always reproducable. He could reproduce it on every page with JPEG images if I understand him correctly. Also, after disabling hardware acceleration he was still having problems, now with (partially) white images.

A lot of the comments later on are talking about what may be a different bug. Perhaps related, but different. This bug is not always reproducable. Sometimes images go black or partially black, but not always. And the problem completely goes away once you disable hardware acceleration. This is basically the bug that I filed on 2015-02-28 four days before this bug was filed: https://bugzilla.mozilla.org/show_bug.cgi?id=1138061

If it's the same bug we would ideally want one the two bugs closed as a duplicate. But if it's a different bug we might want to keep both open.

Comment 23

[Chad Douglas]

Attachment: Corruption of GIF image

The pattern of corruption both Hilltop and I have experienced is remarkably similar. For me it does not happen on all images. At first I thought it was only happening with JPEG images, but I believe I have also seen it with a GIF image* (attached). Like others, disabling hardware acceleration eliminates the problem. I noticed no negative effects from doing this (performance aside).

* https://images-na.ssl-images-amazon.com/images/G/02/gno/images/general/navAmazonLogoFooter._V152929188_.gif

Comment 24

[Chad Douglas]

(In reply to Chad Douglas from comment #23)
> For me it does not happen on all images. At first I thought it was
> only happening with JPEG images, but I believe I have also seen it with a
> GIF image

When I say this I don't mean to imply it was was happening with all JPEG images. Most of them display normally.

Comment 25

[spizzbool]

Might have something to do with Intel HD being the secondary adapter here

Adapter Description	NVIDIA GeForce GTX 560
Adapter Description (GPU #2)	Intel(R) HD Graphics
Adapter Drivers	nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter Drivers (GPU #2)	igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32
Adapter RAM	1024
Adapter RAM (GPU #2)	Unknown
ClearType Parameters	D [ Gamma: 1800 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 400 ] D [ Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 300 ]
Device ID	0x1201
Device ID (GPU #2)	0x0102
Direct2D Enabled	true
DirectWrite Enabled	true (6.3.9600.17415)
Driver Date	3-13-2015
Driver Date (GPU #2)	1-29-2014
Driver Version	9.18.13.4788
Driver Version (GPU #2)	9.17.10.3347
GPU #2 Active	false
GPU Accelerated Windows	2/2 Direct3D 11 (OMTC)
Subsys ID	35271458
Subsys ID (GPU #2)	0000000c
Vendor ID	0x10de
Vendor ID (GPU #2)	0x8086
WebGL Renderer	Google Inc. -- ANGLE (NVIDIA GeForce GTX 560 Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d
AzureContentBackend	direct2d
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0

Comment 26

[pauloelr]

Same issue here on Firefox 36.0.4

[Display]
Operating System:	Windows 8.1 Enterprise, 64-bit
DirectX version:	11.0 
GPU processor:		GeForce GTX 260
Driver version:		340.52
Direct3D API version:	10
CUDA Cores:		216 
Core clock:		626 MHz 
Shader clock:		1350 MHz
Memory data rate:	2106 MHz
Memory interface:	448-bit 
Total available graphics memory:	4095 MB
Dedicated video memory:	896 MB GDDR3
System video memory:	0 MB
Shared system memory:	3199 MB
Video BIOS version:	62.00.4C.00.50
IRQ:			24
Bus:			PCI Express x16 Gen2

Comment 27

[u279076]

I think this is a dupe of bug 1138061 as the symptom and the affected environments seem almost identical. We should focus our efforts in one bug report. We can reopen this bug report if that bug gets resolved and this still reproduces.