Issue metadata
Sign in to add a comment
|
300 x 620 px PNG image rendered incompletely
Reported by
13hu...@gmail.com,
Feb 3 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/64.0.3282.119 Chrome/64.0.3282.119 Safari/537.36 Example URL: https://upload.wikimedia.org/wikipedia/commons/1/1f/Doxygen_ouput.png Steps to reproduce the problem: 1. https://upload.wikimedia.org/wikipedia/commons/1/1f/Doxygen_ouput.png From https://en.wikipedia.org/wiki/Doxygen#/media/File:Doxygen_ouput.png What is the expected behavior? Image loads completely. What went wrong? Only very top part of image is loaded, rest is checkered (see screenshot). Does it occur on multiple sites: N/A Is it a problem with a plugin? N/A Did this work before? N/A Does this work in other browsers? Yes Chrome version: 64.0.3282.119 Channel: stable OS Version: Flash Version: Renders as expected in Firefox
,
Feb 5 2018
Able to reproduce the issue on Windows 10. Mac OS 10.12.6 and Ubuntu 14.04 on the latest Stable 64.0.3282.140 and Dev 65.0.3325.31 by following the steps mentioned in the original comment. Not able to repro this issue on the latest Canary 66.0.3340.0. Hence below is the reverse bisect information. Reverse Bisect Information: ============================ Good build: 64.0.3245.0 (Revision - 510270 ) Bad Build : 64.0.3246.0 (Revision - 510623 ) By executing the per-revision bisect script. below is the Changelog URL. Change Log URL: ================ https://chromium.googlesource.com/chromium/src/+log/2767edcdb266aea34a5fb4354a36d84858244fad..f82653a473f8de5fc86d0f2ecc75f6237e61946b From the above change log suspecting the below change Review-Url: https://chromium-review.googlesource.com/704209 scroggo@@ - Can you please check if the this issue is caused with respect to your change, else help us in assigning to the right owner. Adding ReleaseBlock-Stable as this is a recent regression. Please feel to remove the same if it is not applicable. Thanks..
,
Feb 5 2018
Yes, this is very likely due to the update to 1.6.34, which has been reverted at ToT. This is supported by the fact that the bug is no longer reproducible in 66, but I'll double check. (The revert is due to issue 807324 , which tracks a similar problem with a different png.)
,
Feb 5 2018
,
Feb 5 2018
Yes, this is the same bug, fixed by the revert to the older version. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Feb 4 2018