Closed
Bug 860020
Opened 12 years ago
Closed 12 years ago
PNG that used to load correctly now just prints the filename, and posts "Image corrupt or truncated" to error console
Categories
(Core :: Graphics: ImageLib, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 857040
Tracking | Status | |
---|---|---|
firefox21 | --- | unaffected |
firefox22 | - | affected |
firefox23 | - | affected |
People
(Reporter: dholbert, Assigned: joe)
References
()
Details
(Keywords: regression)
Attachments
(2 files)
STR:
1. Load attachment
EXPECTED RESULTS: image displays. (it's a screenshot of DOM inspector, or something)
ACTUAL RESULTS:
- we print a blue background with the URL of the file printed on top of it
- Error console says "Image corrupt or truncated"
In current beta (ver 21), we get EXPECTED RESULTS.
In current aurora (ver 22) and Nightly, we get ACTUAL RESULTS.
Nightly UA string: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20130408 Firefox/23.0
mozregression gives this range:
{
Last good nightly: 2013-03-21
First bad nightly: 2013-03-22
Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1d6fe70c79c5&tochange=0e9badd3cf39
}
which includes bug 716140. Seems like that that bug or something related to it is the culprit here.
Reporter | ||
Comment 1•12 years ago
|
||
(Note that it does look like there's some sort of issue with the JPG file -- my local image viewer, "eog", says the following when I try to open it:
> Could not load image [filename]
> Error interpreting JPEG image file (Not a JPEG file: starts with 0x89 0x50)
So this could be a case where we've just gotten stricter about our requirements for JPEG files.
Reporter | ||
Comment 2•12 years ago
|
||
(on the other hand, gimp and ImageMagick can open the jpg file just fine)
![]() |
||
Comment 3•12 years ago
|
||
0x89 0x50 is the PNG magic number. In fact, that file is a PNG file (and the server says so, too; it's served as image/png from https://www.evernote.com/shard/s2/sh/4ea41054-3187-4bba-90ee-2b07a24daa2b/41a0a81f5b1405f238e91ab95e058cc2/deep/0/Screenshot%204/9/13%2012:20%20PM.jpg ).
![]() |
||
Updated•12 years ago
|
Attachment #735394 -
Attachment mime type: image/jpeg → image/png
![]() |
||
Updated•12 years ago
|
Summary: JPEG that used to load correctly now just prints the filename, and posts "Image corrupt or truncated" to error console → PNG that used to load correctly now just prints the filename, and posts "Image corrupt or truncated" to error console
Reporter | ||
Comment 4•12 years ago
|
||
Ah, gotcha - thanks for noticing/fixing that! The "jpg" extension in the URL is what threw me off, and it's a red herring anyway -- we can't load it even with the correct extension / mimetype.
So -- with that local file-rename, eog now loads the file correctly, and Firefox nightly & Aurora are the only programs I have that can't load it.
Reporter | ||
Updated•12 years ago
|
Attachment #735394 -
Attachment description: testcase (just a .jpg file) → testcase (just a .png file)
Attachment #735394 -
Attachment filename: jpeg-errors.jpg → png-with-errors.png
Reporter | ||
Comment 5•12 years ago
|
||
Requesting tracking for Firefox 22, since this is a regression on that train right now, preventing some images from rendering properly.
![]() |
||
Updated•12 years ago
|
tracking-firefox23:
--- → ?
Comment 6•12 years ago
|
||
Yep - this should be fully understood before shipping FF22.
Assignee: nobody → joe
status-firefox21:
--- → unaffected
Comment 7•12 years ago
|
||
I am taking a preliminary look at this right now. Will leave assigned to Joe until I determine if I can fix it or not. =)
Comment 8•12 years ago
|
||
Another broken one:
https://www.evernote.com/shard/s4/sh/7aee9ff3-ab7b-40bb-abbb-51f369918ddd/58ca49b9c6b4479d7c2cb1e66f933be4/deep/0/Screenshot%204/12/13%209:43%20PM.jpg
(Also a screenshot on Evernote, also a PNG misnamed as JPG.)
Comment 9•12 years ago
|
||
(Older bug has more technical info and less confusion in the comments. Newer bug has tracking flags and regression info.)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Comment 10•12 years ago
|
||
Comment 11•12 years ago
|
||
verified dupe. The file has an ancillary chunk with invalid (0000) CRC after the IDAT chunk.
Status: RESOLVED → VERIFIED
Updated•12 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•