895954 - Colors are sometimes wrong in Linux with OMTC

Status: RESOLVED WORKSFORME

(Core :: Graphics: Layers, defect)

Description

[Tom S [:evilpie]]

Sometimes images seem to be in the wrong color. People look blue etc.

Comment 1

[Matt Woodrow (:mattwoodrow)]

The URL you saw this on would be useful.

Comment 2

[Tom S [:evilpie]]

http://foodiegossip.blogspot.ca/2013/07/hells-kitchen-winners-where-are-they-now.html This also just reproduced in a new instance.

Comment 3

[Matt Woodrow (:mattwoodrow)]

I can't reproduce this on OSX.

Comment 4

[Tom S [:evilpie]]

I haven't seen this in a while and I can't reproduce it on the linked paged.

Comment 5

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

This is still happening to me pretty regularly.

Comment 6

[Nicolas Silva [:nical]]

This look like our typical swapped RB channels bug. We tend to consider pixel formats as if R and B were swapped and manually swap them in the shader in the end when compositing. Jeff knows more than me about this I think.

Comment 7

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

This happens to me quite often when using OMTC on Linux with an nvidia driver. Please let me know if I can help to debug it. It's gotten to the point where I don't even know what color anything is supposed to be.

Comment 8

[Jeff Muizelaar [:jrmuizel]]

I'm not sure how to help here and don't have time to look at this in more detail right now.

Comment 9

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

I'm changing the bug title to reflect the fact that this isn't specific to e10s. It happens to anyone who wants to use OMTC on Linux.

Comment 11

[Robert Kaiser]

In bug 908859, :johns saw this with binary NVidia and open-source radeon drivers, with or without hardware acceleration, and I'm still seeing with with open-source Intel graphics drivers. So it's not the drivers or chipsets.

I can pretty consistently see this in the graph on https://crash-stats.mozilla.com/daily?p=Firefox

Comment 12

[John Schoenick [:johns]]

It looks like this may be fixed by bug 910488 (bug 910488 comment 5)

Comment 13

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

I think Matt eventually fixed this for real, but I can't remember the bug number.