User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060326 Firefox/1.5.0.3 (Debian-1.5.dfsg+1.5.0.3-2) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060326 Firefox/1.5.0.3 (Debian-1.5.dfsg+1.5.0.3-2) The image noted above is an example from an itro to PNG: http://www.libpng.org/pub/png/pngintro.html It is 512x32768 and displays every posible color When I try to display it, I get the error indicated in the summary for Firefox 1.5.0.3: The image “http://www.libpng.org/pub/png/img_png/16million.png” cannot be displayed, because it contains errors. This occurs both when downloading from the website and when saved to /tmp/. It loads and displays just fine into GIMP 2.2.11, GQview 2.0.1 and Konqueror: 3.5.2 (( this is under Knoppix 5.0.1 DVD with Qt: 3.3.6 KDE: 3.5.2 )) For minefield (Downloaded June 12, 2006) firefox-3.0a1.en-US.linux-i686.tar.bz2 it dies with an X11 error.. (see below) Reproducible: Always Steps to Reproduce: 1. click on image URL Actual Results: The image “http://www.libpng.org/pub/png/img_png/16million.png” cannot be displayed, because it contains errors. ( firefox 1.5.0.3 ) or: ( X failure (minefield firefox-3.0a1.en-US.linux-i686.tar.bz2 June 12/2006) The program 'Gecko' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 20540 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Expected Results: display image. Tried under failsafe mode. Doesn't seem to help.

MAY be related to bug #341289

The image doesn't display here too with no error messages (scaled 1%) and if I click where the image should be, the image is displayed as a black box. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060612 Minefield/3.0a1 ID:2006061205 [cairo] -> dupe of bug 315263 ?

(In reply to comment #2) > -> dupe of bug 315263 ? > Image from this bug displays quite nicely (and quickly) under Windows The large image indicated under bug 315263 displays (slowly, but OK) under Linux, but shows a block box on Windows ( Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4) curiouser and curioser.

Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9a1) Gecko/20060610 Minefield/3.0a1 - Build ID: 0000000000 Firefox crashes for me when loading the image: WARNING: NS_ENSURE_TRUE(shell) failed: file /home/philip/Work/Mozilla/mozilla/content/base/src/nsImageLoadingContent.cpp, line 842 The program 'Gecko' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 63181 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

*** This bug has been marked as a duplicate of 210931 ***

I would be inclined to reopen this as a different bug. The X blowups are probably due to the underlying error causing X to barf, but my original report (The image <FOO> cannot be displayed, because it contains errors.) is due to Mozilla realizing that there is a problem somewhere. This indicates that the underlying problem is NOT with gtk/x getting the error before Mozilla does -- and the underlying error in the PNG rendering under Linux needs to be addressed.

your original report included two symptoms. as a result, your bug was resolved as a duplicate of one of them. it's not our fault that we agreed with you. further, as you clearly indicated, the xerror is the result w/ current builds. we generally don't spend time fixing errant behavior on branches, especially non crashers.