User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:188.8.131.52) Gecko/20061204 Firefox/184.108.40.206 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:220.127.116.11) Gecko/20061204 Firefox/18.104.22.168 Large pictures are not loaded and displayed. I tried FireFox 22.214.171.124 on two systems : - system A : Athlon 1400MHz 1 GB RAM, Windows 2003 SP1 - system B : Core2Duo T7200, 2 GB RAM, Windows XP Pro SP2 http://imgsrc.hubblesite.org/hu/db/2003/28/images/a/formats/full_jpg.jpg loads on both systems http://imgsrc.hubblesite.org/hu/db/2006/10/images/a/formats/full_jpg.jpg loads on system A, but not system B. System B shows an empty page http://imgsrc.hubblesite.org/hu/db/2006/01/images/a/formats/full_jpg.jpg both systems show the text : The image "http://imgsrc.hubblesite.org/hu/db/2006/01/images/a/formats/full_jpg.jpg" cannot be displayed, because it contains errors. http://imgsrc.hubblesite.org/hu/db/2003/11/images/a/formats/full_jpg.jpg both systems show the text : The image "http://imgsrc.hubblesite.org/hu/db/2003/11/images/a/formats/full_jpg.jpg" cannot be displayed, because it contains errors. All images open if downloaded and opened with Windows Picture Viewer (and it opens them faster than firefox). There are more images to test at http://hubblesite.org/ and http://hiroc.lpl.arizona.edu/images/PSP/ Reproducible: Always Actual Results: Image not displayed, but blank page or page with error text. Expected Results: Image displayed.
http://imgsrc.hubblesite.org/hu/db/2006/01/images/a/formats/full_jpg.jpg crashes badly. Incident ID: 29442116 Stack Signature kernel32.dll + 0x12a5b (0x7c812a5b) e5b9d159 Product ID FirefoxTrunk Build ID 2007021704 Trigger Time 2007-02-18 00:59:16.0 Platform Win32 Operating System Windows NT 5.1 build 2600 Module kernel32.dll + (00012a5b) URL visited User Comments Since Last Crash 10 sec Total Uptime 32122 sec Trigger Reason Microsoft C++ exception Source File, Line No. N/A Stack Trace kernel32.dll + 0x12a5b (0x7c812a5b) MSVCR80.dll + 0x28dd3 (0x78158dd3) MSVCR80.dll + 0x30e59 (0x78160e59) gfxImageSurface::gfxImageSurface [mozilla\gfx\thebes\src\gfximagesurface.cpp, line 54] gfxImageFrame::Init [mozilla\gfx\src\shared\gfximageframe.cpp, line 142] nsJPEGDecoder::WriteFrom [mozilla\modules\libpr0n\decoders\jpeg\nsjpegdecoder.cpp, line 303] imgRequest::OnDataAvailable [mozilla\modules\libpr0n\src\imgrequest.cpp, line 903] Dupe of / related to bug 210931 ?
Similar results here on a Core Duo T2500 w/1GB RAM on Seamonkey: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20070222 SeaMonkey/1.1.1 no errors on http://imgsrc.hubblesite.org/hu/db/2003/28/images/a/formats/full_jpg.jpg or http://imgsrc.hubblesite.org/hu/db/2006/10/images/a/formats/full_jpg.jpg http://imgsrc.hubblesite.org/hu/db/2006/01/images/a/formats/full_jpg.jpg gave me a "Page Load Error" response, with a body of "Connection Interrupted The document contains no data. The network link was interrupted while negotiating a connection. Please try again." The last one returned: The image "http://imgsrc.hubblesite.org/hu/db/2003/11/images/a/formats/full_jpg.jpg" cannot be displayed, because it contains errors.
WFM Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:188.8.131.52) Gecko/2008091620 Firefox/3.0.2 still see this?
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/2008092417 Firefox/3.0.3 Windows XP Professional SP3 , 32 bit First none of the four images from the initial report worked. They all gave the "because it contains errors.". I had a lot of tabs open and firefox was running for a long time. So I closed all and restarted FF with only one window/tab. Then the first two images loaded and displayed correctly. But the second two not. So this bug is still present.
I get different various results, including 1) image displays correctly 2) preview image displays with missing chunks, but expanding it out and back again fixes the problem 3) last night with multiple tabs open I was getting the contains errors messages In IE7, I'm seeing the images sometimes, and sometimes I'm getting http 501 errors. Oddly enough all of the images can be saved correctly using the context menu.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11) Gecko/20100401 Firefox/3.6.3 Intel Core 2 Duo-2302 - 2 GB RAM - Windows XP Pro SP3 http://imgsrc.hubblesite.org/hu/db/2003/28/images/a/formats/full_jpg.jpg loads OK. http://imgsrc.hubblesite.org/hu/db/2006/01/images/a/formats/full_jpg.jpg ==> The image cannot be displayed, because it contains errors" http://imgsrc.hubblesite.org/hu/db/2006/10/images/a/formats/full_jpg.jpg ==> The image cannot be displayed, because it contains errors" http://imgsrc.hubblesite.org/hu/db/2003/11/images/a/formats/full_jpg.jpg ==> The image cannot be displayed, because it contains errors" FYI, I've been able to reproduce the above errors using Google Chrome 4.1.x except for /2006/10/ image that loads OK.
I can reproduce these errors on Firefox 9 on XP, but not on OS X.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0a1) Gecko/20120105 Firefox/12.0a1 I'm currently unable to reproduce this in a nightly with the images provided in comment 6. Can anyone else confirm?
(In reply to Jim Mathies [:jimm] from comment #8) > Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0a1) Gecko/20120105 Firefox/12.0a1 > > I'm currently unable to reproduce this in a nightly with the images provided > in comment 6. Can anyone else confirm? With latest nightly I can't reproduce on Windows 7 64-bit, but I can reproduce all comment 6 on Windows XP.
Someone should mark bug 941823 as a duplicate of this bug.
As per bug 941823 comment 12, this should be resolved when bug 1045926 gets implemented.
I've been encountering this bug since mid-2010. If the bug isn't going to be fixed could someone please at least change the error message so that it doesn't give the impression that the image is at fault; that it "contains errors" (http://i.imgur.com/I2L3pTl.png) Also, I have a question (I don't require an answer but it would be nice): How is it that so many new features were added to Firefox over the past six years but this obnoxious bug remained in place? I would think eliminating bugs from the browser would take priority over adding new features.