Created attachment 14113 [details] Image 8177x1 pixel, make firefox crash Hi, with Nouveau, image greater than 8176 pixel make firefox (2.x and 3.0) crash with this error : 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 2281 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.) Konqueror doesn't crash but doesn't display the image and print : X Error: BadAlloc (insufficient resources for operation) 11 Major opcode: 53 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 155 Minor opcode: 4 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 Minor opcode: 0 Resource id: 0x26003c3 X Error of failed request: RenderBadPicture (invalid Picture parameter) Major opcode of failed request: 155 (RENDER) Minor opcode of failed request: 7 (RenderFreePicture) Picture id in failed request: 0x26003c6 Serial number of failed request: 9414 Current serial number in output stream: 9827 Opera display the image fine With nv driver and proprietary nvidia driver, firefox displays the image and doesn't crash. I don't see anything in logs related to this problem (though I didn't insert drm with debug option).
real website which exhibit the bug (as reported by gQuigs http://people.freedesktop.org/~ahuillet/irclogs/nouveau-2008-02-03.htm#0522 ) www.howtoforge.com
The bug is hopefully gone now, but please verify.
Bug still here with latest git (same error) :/ commit 9d9a5acae1deae8c76b512362634066e0c32a817 Author: Jaime Velasco Juan <jsagarribay@gmail.com> Date: Sun Feb 3 15:45:32 2008 +0100 Don't FIRE_RING() when in NoAccel mode. I just inserted drm with debug=1 et no relevant message appears in syslog/dmesg
I couldn't reproduce your issue and i'm not sure what the issue is.
I'm using Xserver 1.3 (Xorg 7.2) on x86_64 arch. With option NoAccel, the bug doesn't occur, so it may be related to EXA. If I remember correctly, you are using Xserver 1.4.x, maybe it's a bug already fixed in this release.
Still an issue?
(In reply to comment #6) > Still an issue? > yes, still occurs with fresh git
Using Xorg 7.3 / Xserver 1.4 and today git, it still crashs with: The program 'firefox-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 22204 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 should be fixed in xserver commit bc2d516f16d94c805b4dfa8e5b9eef40ff0cbe98, which is part of the upcoming 1.5 release. Please reopen if that turns out not to be the case.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.