[Regression] Chrome/56.0.2924.76 causes images to display in Colour Burn (i.e badly)
Reported by
markhad...@markhadden.co.uk,
Jan 31 2017
|
|||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36 Example URL: www.markhaddenphotography.com Steps to reproduce the problem: 1. update to latest chrome 2. login to facebook 3. or my own site at www.markhaddenphotography.com What is the expected behavior? images should display normally. What went wrong? no idea. i gather it might be something to do with me having montior calibrated icc profiles. one is attached but specific to my dell monitor. also attached is an example of what the images look like. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 56.0.2924.76 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0
,
Jan 31 2017
Ive also re calibrated, changed profiles, re installed chrome clean, searched numerous forums etc etc. In the end i dropped back to the last version, which worked fine for me.
,
Feb 1 2017
+noel@ who knows a lot about coloring in Chrome.
,
Feb 1 2017
#1 I got exactly the same issue with severe colour clipping in the shadows of images ... Ok Kia thanks. You might have the same problem as Mark (not sure yet). Let me deal with Marks question first, and then come back to you if that's ok.
,
Feb 1 2017
Thanks for the report Mark. #3 Mark mentioned: >Ive also re calibrated, changed profiles, re installed chrome clean, searched numerous forums etc etc. In the end i dropped back to the last version, which worked fine for me. Apologies. The previous version worked fine (Chrome 54) for you, and thank you for that detail. Based on that, this appears to be a regression in Chrome/55.0.2883.75. Updating the bug title to reflect that.
,
Feb 1 2017
,
Feb 1 2017
Adding folks who have been making code changes in this area.
,
Feb 1 2017
Mark, a few things needed from you to move this bug along > Steps to reproduce the problem: > 1. update to latest chrome > 2. login to facebook > 3. or my own site at www.markhaddenphotography.com 1) Take a screen shot of one of the images affected from your facebook site and attach that screen shot here. 2) Attach the affected image from your facebook site here. 3) Attach the color profile you were using when the image was affected.
,
Feb 1 2017
,
Feb 1 2017
HI Please see attached screenshots from my own website and also from facebook page. I have shown on each image a comparison between the versions so you can see the difference. Also attached is my monitor profile. thanks mark
,
Feb 1 2017
Right, I can sure see the clipping. On your facebook page, let's choose an image from there so we can test with it. How about the image of the clown fish? While on your facebook page, right-click that image and save it to your desktop. Then attach that image here.
,
Feb 1 2017
see attached. ive included the original but maybe theres no difference between them.
,
Feb 1 2017
And BTW, it doesn't matter what version of chrome you view with for this step: just _right-click save_ the clown fish image from your facebook page and attach it here. (I want the clown fish image that facebook is serving).
,
Feb 1 2017
We crossed a litter there, but clownfish + Shrimp facebook.jpg looks to be the test image, thanks. You can confirm when ready, but here's the test. Download the image from this chrome bug (see the download link) and drop the image on Chrome 55 with your color profile installed. You should see the color burn effect in the image, right?
,
Feb 1 2017
which image am i downloading?
,
Feb 1 2017
just re read one of your comments above. the problem i have is with the latest version 56.0.2924.76. Version 55.0.2883.75 is fine for me as were all previous versions. Not sure about 54 but i guess i had it at some point on the past.
,
Feb 1 2017
#20 > just re read one of your comments above. the problem i have is with the latest version 56.0.2924.76. Version 55.0.2883.75 is fine for me as were all previous versions. Gothca, 56.0.2924.76 is the problem, will update the bug title. #19 > which image am i downloading? clownfish + Shrimp facebook.jpg, the first image in #16. Click it's download link, and then drag-drop the downloaded image into Chrome 56.0.2924.76. You should see the burn effect.
,
Feb 1 2017
yes indeed. the burn is there.
,
Feb 1 2017
Good, thanks Mark. We have the right images (you see the burn). 56.0.2924.76 is Chrome Beta. I installed it on Windows 10. I then installed your color profile from #10 on my monitors. I started 56.0.2924.76 Chrome Beta and loaded the test image. I also installed Chrome Canary 58.0.2998.0 and loaded the image in it also. Here is the side-by-side image I see ...
,
Feb 1 2017
The image on the left: Chrome 56 beta, has the burn effect you describe, and that confirms this bug. The image on the right: seems to be fixed in Chrome 58. Nonetheless, there is clear regression in Chrome 56 beta which will soon be promoted to Chrome stable.
,
Feb 1 2017
i downloaded chrome from the https://www.google.com/chrome/browser/desktop/index.html page (not beta) and it gave me that version. I did try also the beta version that i found and indeed had the same build number. I guess thats why there were the same issues with both. here: https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html it says its already promoted to stable. And for sure thats when my problems started. Anyway I will stick with 55 for now i gues.
,
Feb 1 2017
I was just reinstalling Chrome stable myself from the official page, and I agree, it has just been promoted to 56.0.2924.76 (Official Build) (64-bit). Alas, this bug has reached Chrome stable, I see the burn effect there.
,
Feb 1 2017
Just tested Chrome 57.0.2987.19 dev (64-bit), and no bug. This bug exists in Chrome 56.0.2924.76 only.
,
Feb 1 2017
@kla_pro_bean #1 Haven't forgotten you, and you mentioned > Chrome version: 56.0.2924.76 > Windows 10 (latest update) Yeap, looks to me like you have this bug too. Bear with us while we get a bisect done, to work out which code change caused this regression.
,
Feb 1 2017
I suspect the bug is in Skia somewhere. Matt could you take a look, or reassign please?
,
Feb 2 2017
Mac Chrome Stable 56.0.2924.87 (64-bit) also has this issue.
,
Feb 2 2017
,
Feb 2 2017
Unable to reproduce the issue on windows 7,windows 10 and Mac 10.12.2 using chrome version 56.0.2924.87 and canary 58.0.2997.0 with the below steps 1.Opened the image clownfish + Shrimp facebook.jpg from comment #16 2.Not observed any burn effect Please find the attached screen shot of chrome 56.0.2924.87 (left) and 58.0.2997.0 (right) Please confirm if anything missed here in reproducing the issue. Thanks,
,
Feb 2 2017
#32 >
> 1.Opened the image clownfish + Shrimp facebook.jpg from comment #16
> 2.Not observed any burn effect
> Please confirm if anything missed here in reproducing the issue.
Yeah, some steps missed.
1) Install the color profile from #10 on your monitor(s)
DELL U2413_july2016.icm
2) Force Quit / Exit Chrome 56 and Canary 58
3) Restart Chrome 56 and Canary 58
4) Load the test image in Chrome 56 and Canary 58
Expected result: the images should look identical.
Actual result: the image in Chrome 56 is noticeably darker and less detailed compared to the image in Chrome 58.
,
Feb 2 2017
I'm happy to look into this. Will not be until Monday though, as I'm out of town.
,
Feb 3 2017
Ok Matt, thanks. The reproduction steps are bit fiddly, so I'll do the bisect myself. Chrome 55.0.2883.79 is revision 423768 Chrome 56.0.2924.79 is revision 433059 ./tools/bisect-builds.py -a mac -g 423768 -b 433059 \ --use-local-cache -- --no-first-run --user-data-dir=/tmp You are probably looking for a change made after 426836 (known good), but no later than 426862 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/15d04a3473cb60cba6ceb7205353df67642126f7..f1aa7d4e5ec785cc01875b4eecf46844161d6d3c
,
Feb 3 2017
,
Feb 6 2017
Issue 688644 has been merged into this issue.
,
Feb 6 2017
Uggh I should have seen this coming... The ICC profile spec allows for parametric transfer functions to be specified as equations (http://www.color.org/icc_specs2.xalter): Y = (aX + b)^g + c (X >= d) Y = (cX + f) (X < d) With the obvious error that "c" is used twice in those equations and "e" is used zero times. Skia (meaning myself) assumed the intended interpretation was: Y = (aX + b)^g + c (X >= d) Y = (eX + f) (X < d) This however turned out the be wrong. On reading the ICC errata, the "corrected" equations are: Y = (aX + b)^g + e (X >= d) Y = (cX + f) (X < d) The profile attached in #10 is one of the rare profiles where the interpretation of "c" and "e" really counts. a = 0.985, b = 0.015, c = 0.033, d = 0.063, e = 0.000, f = 0.001, g = 2.212 I've already fixed this in https://skia-review.googlesource.com/c/6277/ (thus, this is only a m56 bug). At the time, I thought this was only a logical bug - I didn't realize that naming the variables incorrectly was also causing me to use them incorrectly. I can cherry-pick back to m56 (and fix merge conflicts) if that's the right way to handle this. Do we know who is the correct person to triage this for m56?
,
Feb 7 2017
just dropping a message here: I have the exact same issue Color burn on Image with embedded rgb profile). Images with no profile are displayed correctly. On a side note, This issue also started on the Steam Browser (the game plateform UI) few days ago. I believe it uses chromium too.
,
Feb 7 2017
Forgot to say: Windows 7 x64, fully up to date, nvidia driver uptodate, latest regular google chrome 56.0.2924.87 (64-bit)
,
Feb 7 2017
update: the issue occurs only if a monitor color profile is set in the windows color management. I tried with no profile, and everything is OK. Problem: I need the profile for my work.
,
Feb 7 2017
kavvaru@ do you know who can triage this for m56?
,
Feb 8 2017
@Noel I got the same problem, just switched to chrome today, from firefox. i also got a color calibrated profile for my 2 screens. Tho my bug do not hit all images, but i guess its up to the type of ing, seems to hit .png more than others. any eta on bug fix?
,
Feb 8 2017
#43 zax1990@ > i also got a color calibrated profile for my 2 screens. IC, could you add the color profile from your primary screen (the one chrome started on) to this bug? > any eta on bug fix? Sorry, no eta as yet. #41 mguffin@, > the issue occurs only if a monitor color profile is set in the windows color management Could you attach your monitor color profile to this bug, please?
,
Feb 8 2017
Requesting M56 merge evaluation for the fix in C#38.
,
Feb 8 2017
Having the same issue, noticed primarily through EA's Battlelog on the soldier portraits. Have a calibrated ICC for my Dell S2417DG applied using 56.0.2924.87 64-bit Chrome, switching over to IE displays no issues - See the attached pic, Chrome on the left and IE on the right.
,
Feb 8 2017
Same here. Chrome messes up colors big time on both regular and adobe RGB displays alike. It seems not all images are messed up. For example the previews in photos do appear well. Opening the image produces the color clipping. The attachment shows Internet Explorer next to Chrome (right). As you can see chrome is complete mess. Here is shared link to the image in the attachment on google photos. https://goo.gl/photos/PV5hmtV2do7B4bRw5
,
Feb 8 2017
In comment #47 I used Chrome 56.0.2924.87
,
Feb 9 2017
after further exploration (see Comment #47) the issue seems to affect images with embedded color profile. When I export image without profile form photoshop it shows up correctly. Problem is that RAW programs such as Lightroom and Capture One cannot export JPG files without color profile in them...... I use windows 8 64-bit. The image in the example has been processed using CaptureOne 10. I reproduced using export from photoshop with embedded color profile.
,
Feb 9 2017
#49 karaatanasov Yes images with a color profile are affected. We beleive the problem is caused by your screen color profile. Could you attach your screen color profile to this bug please?
,
Feb 9 2017
I also see this issue with Chrome 56.0.2924.87 (64-bit) on Windows 10. I'm attaching the color profiles of my two screens, both of which seem to suffer from this (unless Chrome only takes into consideration the profile of the screen it was started on, in which case it'd probably be FS2434.icm).
,
Feb 9 2017
Here's my Dell colour profile which has the problem with colours. The funny thing is this is only a recent issue, I've had the monitor for months and had zero issues with chrome until I noticed maybe the middle of last week.
,
Feb 9 2017
As requested here is my monitor color profile.
,
Feb 9 2017
This issue just "burned" me a couple days ago. System has been running fine for months, and then spontaneously, Chrome decides to start displaying images with the darks severely clipped. I made NO changes to system settings, I installed NO update to Chrome, just one day Chrome decided to break images. Everything worked fine in Firefox and Edge, it was only Chrome that was ruining everything. Removing my monitor ICC profile in Windows 10 Color Management (which had been generated using an x-rite i1Display Pro) "fixed" the issue, although I'd hardly call that a fix. I'm so sick and tired of Chrome's awful color management. How many years do we have to suffer through this before it gets resolved?
,
Feb 9 2017
I can confirm image burn on Chrome Version 56.0.2924.87 (64-bit). Just began 2 days ago after upgrading to latest version of Chrome. See screenshot running Chrome and MS Edge sidexside. I have a custom calibrated monitor (I'm a pro photographer). Running Windows 10 65 bit. What is the workaround until a new version of Chrome is released to fix the issue? Since my livelihood depends on correct colors for presentation (I present to clients using the Chrome browser), what should I do? Thanks for your help! -Michael
,
Feb 9 2017
Hey @fpzmedia.com - when you removed the icc profile to "fix" the issue, did you run ANOTHER i1 calibration? And did that new calibration also show signs of the image burn?
,
Feb 9 2017
Approved for merge into M56
,
Feb 9 2017
The following revision refers to this bug: https://skia.googlesource.com/skia/+/dd45f8195783efc7b8044b006eae5ea5ac127cc2 commit dd45f8195783efc7b8044b006eae5ea5ac127cc2 Author: Matt Sarett <msarett@google.com> Date: Thu Feb 09 18:15:33 2017 Fix swapped interpretation of c and e in SkColorSpace_ICC [m56] The ICC errata supports the opposite of what we do. http://www.color.org/icc_specs2.xalter BUG:687194 GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=8257 NOTREECHECKS=true NOTRY=true NOPRESUBMIT=true CQ_INCLUDE_TRYBOTS=master.client.skia:Test-Ubuntu-GCC-GCE-CPU-AVX2-x86_64-Release-SKNX_NO_SIMD-Trybot Change-Id: Id363969e15ba12832acb2736e61face10eefe01a Reviewed-on: https://skia-review.googlesource.com/8257 Reviewed-by: Matt Sarett <msarett@google.com> Commit-Queue: Matt Sarett <msarett@google.com> [modify] https://crrev.com/dd45f8195783efc7b8044b006eae5ea5ac127cc2/tests/ColorSpaceXformTest.cpp [modify] https://crrev.com/dd45f8195783efc7b8044b006eae5ea5ac127cc2/src/core/SkColorSpacePriv.h [modify] https://crrev.com/dd45f8195783efc7b8044b006eae5ea5ac127cc2/src/opts/SkRasterPipeline_opts.h [modify] https://crrev.com/dd45f8195783efc7b8044b006eae5ea5ac127cc2/src/core/SkColorSpace_ICC.cpp [modify] https://crrev.com/dd45f8195783efc7b8044b006eae5ea5ac127cc2/src/core/SkColorSpaceXform_A2B.cpp [modify] https://crrev.com/dd45f8195783efc7b8044b006eae5ea5ac127cc2/src/core/SkColorSpaceXform.cpp [modify] https://crrev.com/dd45f8195783efc7b8044b006eae5ea5ac127cc2/include/core/SkColorSpace.h [modify] https://crrev.com/dd45f8195783efc7b8044b006eae5ea5ac127cc2/tests/ColorSpaceTest.cpp
,
Feb 9 2017
"What is the workaround until a new version of Chrome is released to fix the issue?" I'm not sure when m56+fix will be released. m55 and m57 are fine. You can also work around by configuring your monitor to use an ICC profile that does not use the full parametric representation for the transfer function (more detail is in #38). Sorry for the inconvenience, I hope this helps.
,
Feb 9 2017
#50 Noel, find the profiles for both of my monitors attached. I am not quite sure how the Dell profile is used. The monitor supports hardware profiles and supposedly the calibration profile should be loaded somehow in the monitor? I use i1 Display Pro with i1Profiler software to generate my monitor profiles once in a while (monthly). I last used version 1.6.3.18511 of i1Profiler Let me know if I can give you any more valuable information. Should I try using default profiles in windows?
,
Feb 9 2017
workaround: use chrome canary
,
Feb 10 2017
Per comment #59, M57 is fine so no merge is needed, correct?
,
Feb 10 2017
Yes, the fix had already landed before we branched for m57. This was a cherry-pick back to m56.
,
Feb 10 2017
Ok, thank you for confirmation msarett@.
,
Feb 11 2017
To the users that provided their color profiles, thank you. They have parametric type-4 gamma curves with low or 0 "e" value (refer to #38) and would therefore hit this bug. Fix is in, and will be out maybe in a week or so. Meanwhile, it's fixed in Chrome 57 already, so you can workaround the bug by installing Chrome Beta (Chrome 57) [1] [1] http://lmgtfy.com/?q=install+google+chrome+beta
,
Feb 13 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 13 2017
,
Apr 8 2017
Im still having wrong colors in Version 57.0.2987.133 (64-bit).
,
Apr 8 2017
try to install chrome 57 beta and than 57 stable
,
Apr 10 2017
I still have this problem. Version 57.0.2987.133
,
Apr 10 2017
@gigake, @info.auroralights, can you please attach your monitor ICC profile? And an image that is displaying incorrectly?
,
May 20 2017
Still have a problem Windows 10.0.15063.296 Google Chrome Stable 58.0.3029.110 Google Chrome Canary 60.0.3104.0
,
May 20 2017
The images that was used above: https://500px.com/photo/212620185/portrait-by-maxim-maximov https://500px.com/photo/195299651/tanya-by-zachar-rise And there are a lot more.
,
May 22 2017
Note the request for the monitor ICC profile (comment 71). We need that to move forward.
,
May 22 2017
@antoon Can you describe the problem you are seeing? Is it the subtle differences between the images in m58 and m60? Also, can you file a new bug? This seems to me to be unrelated to this issue.
,
Jun 5 2017
The NextAction date has arrived: 2017-06-05
,
Sep 13 2017
I still have a problem with a 61version chrome. I'm using a Benq xl2430t monitor and when I use a custom icc profile, it appears.
,
Sep 13 2017
yark85@ lloks like it's not this issue (which was about color burning, and the images you added don't have that problem). Could you please file a new issue?
,
Sep 13 2017
These are my twitch tv screens. Basically, every website looks too much white. I've been using icc profile more than a year with same monitor and computer. This issue happened after I format my computer a few days ago. I guess I was using old version chrome before I format it. When I use chrome canary, everything is fine with icc profile but with original chrome, I can't use icc profile because of this issue.
,
Sep 13 2017
There is new work involving color correction in Chrome 61, and I suspect that it is changed things for your setup. If you could please open a new bug describing the problem you are having, that would help us identify the exact problem. Please add your screen color profile to the bug, if possible, and mention which OS you are using (Windows, Mac-OSX, Linux, etc).
,
Sep 13 2017
I'm using windows 7 and I attached my icc profile that I downloaded here. http://www.displaylag.com/icc-profiles/ What do you mean that opening a new bug describing the problem? How can I do that? please let me know. Thank you!
,
Sep 13 2017
Windows7 x64
,
Sep 15 2017
yark85@ Thanks for the details. > What do you mean that opening a new bug describing the problem? How can I do that? please let me know. Thank you! I opened the bug for you. Navigate your browser to https://bugs.chromium.org/p/chromium/issues/detail?id=765628
,
Sep 15 2017
Oh, you reported my issue to get help for me. So should I wait for answer from chrome support team? Thanks a lot! I thought you are one of the support team members :D
,
Sep 19 2017
Hi, I've got the same issue (all the colors are darkened and over saturated). Firefox (55.0.2 (64-bit)) and Opera (47.0.2631.80) are displaying colors/images correctly. Environment: - Ubuntu 16.04.3 LTS (x86_64; Unity) - Google Chrome 61.0.3163.91 Thanks!
,
Sep 19 2017
I've just tried Chromium Version 60.0.3112.113 (Developer Build) and everything is fine there.
,
Sep 22 2017
Chromium Version 61.0.3163.79 has the same issue now.
,
Sep 22 2017
Do not put new issues in this bug -- it just muddles things. Please file new bugs. Include screenshots of the behavior, and attach your machine's monitor color profile.
,
Feb 26 2018
Have the same bug with Chrome OS X 64.0.3282.167 64-bit Bug appears on some video streams on twitch.tv |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by kla_pro_...@hotmail.com
, Jan 31 2017921 KB
921 KB View Download