Certain PNG files do not render correctly
Reported by
ian.camp...@gmail.com,
Mar 16 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Example URL: https://images.rakb.link/24498/24498_img1.png Steps to reproduce the problem: 1. Navigate to https://images.rakb.link/24498/24498_img1.png 2. See a square of smaller white and grey squares instead of an actual image What is the expected behavior? Display an image with text and a highlighted specification. What went wrong? chrome did not display the image correctly. If i right click on the square with smaller white and grey squares and click save picture as.. then I am able to open the png file in microsoft picture viewer and it displays correctly. Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 64.0.3282.186 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Mar 19 2018
The image is corrupted according to Adobe Photoshop, ImageMagick, and 5 other image viewers/editors I've tried. Only one app managed to open this file (FastStone viewer).
,
Mar 19 2018
It can be opened in the built-in Windows viewer, IE, MS Office apps.
,
Mar 19 2018
,
Apr 9 2018
Thanks for filing the issue! Able to reproduce the issue on reported chrome version 64.0.3282.186 and on the latest canary 67.0.3390.0 using Windows 10, Ubuntu 14.04 and Mac 10.13.1. As the issue is seen from M60(60.0.3072.0) considering it as Non-regression and marking it as Untriaged.
,
Apr 9 2018
I agree that this image is corrupt. libpng reports a benign error ("IDAT: ADLER32 checksum mismatch" - this is with libpng 1.6.34. Prior to that, we were using 1.6.22, where it would have just been a regular png_error) on the first IDAT, before ever decoding any rows. Then there are lots of warnings stating "Extra compression data in IDAT".
GIMP (2.8.20) opens the file as all black, my Linux ImageViewer opens it as gray, and FireFox (52.6.0 (64-bit)) opens it as white. All seem to agree that this file doesn't have anything meaningful in it.
|
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Mar 19 2018