New issue
Advanced search Search tips

Issue 867093 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 847024
Owner: ----
Closed: Jul 25
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

REGRESSION - Chrome shows Yellow/Sepia color in one of the monitors

Reported by nunomigu...@gmail.com, Jul 24

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36

Steps to reproduce the problem:
1. Open Google Chrome
2. Move Chrome to an affected monitor/screen

What is the expected behavior?
Show real colors as usual.

What went wrong?
Since this version of Google Chrome, one of my screens are making Chrome show as yellow/sepia color, affecting everything in the application.

While I'm moving from one screen to another, Google Chrome intentionally changes the colors by itself. This is obviously a "feature" of Chrome rather than color configuration in my other screen. See screenshots attached.

Did this work before? Yes Previous Stable version

Chrome version: 68.0.3440.75  Channel: stable
OS Version: 10.0
Flash Version: 

The monitor affected is an AOC 2250.
 
sshot-2018-07-24-22-01-45-1.jpg
131 KB View Download
sshot-2018-07-24-22-09-46-1.jpg
62.3 KB View Download
Disabling Hardware Acceleration in Chrome Settings "fixes" the problem.

I saw that suggested in someone's post reporting the exact same problem on Chrome 32:

https://productforums.google.com/forum/#!topic/chrome/q-JKQelC1E8
Labels: Needs-Triage-M68 Needs-Bisect

Comment 4 Deleted

So, this was known since it was in DEV channel, and you still released this problem?... you might get a number of users moving to another browser, if they don't figure out how to get rid of this problem.

I suggest you have something on Chrome settings (or somehow detect that Chrome became "yellow"), so users can get instructions on how to fix the problem (similar to what you have in the document above), or even better, make Chrome fix the problem for the user automatically.
Cc: viswa.karala@chromium.org
Labels: Triaged-ET
Unable to reproduce the issue on chrome reported version# 68.0.3440.75 using Windows-10 & 7.

This issue seems to be similar to Issue:  847024  and which is resolved by disabling the Hardware Acceleration in chrome://settings or forcing the sRGB colour profile on chrome://flags. CC'ing brianosman@chromium.org and ccameron@chromium.org for help in more inputs on we can dupe this into issue:  847024 .

Thanks!
Yes - that's what I did, and that's definitely a duplicate.

However, do you expect all your affected users to figure out that by themselves?

Hence I'm suggesting that Chrome could detect and do that for the users (after their permission, etc).


If users see that Chrome shows as "yellow" for them, many users might just think that Chrome is broken and possibly give it up.
Mergedinto: 847024
Status: Duplicate (was: Unconfirmed)
Comment #2 is correct, this appears to be a duplicate report.

Sign in to add a comment