[hardy] firefox breaks on some pages with an X error

Bug #194782 reported by Pär
2
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: firefox-3.0

I get this with firefox-3.0 on Hardy.

I tried to set a breakpoint in gdb according discussion in one of the upstream bug reports with the result below:

...
(gdb) break exit
Breakpoint 1 at 0xb7d56e66
(gdb) continue
Continuing.
[New Thread 0xb0fffb90 (LWP 30126)]
[Thread 0xb21c0b90 (LWP 30094) exited]
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 106706 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.)

Breakpoint 1, 0xb7d56e66 in exit () from /lib/tls/i686/cmov/libc.so.6
(gdb) backtrace
#0 0xb7d56e66 in exit () from /lib/tls/i686/cmov/libc.so.6
#1 0xb674a637 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#2 0x00000001 in ?? ()
#3 0xb677b877 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#4 0x091a0158 in ?? ()
#5 0x0001a0d2 in ?? ()
#6 0x0000000b in ?? ()
#7 0x00000035 in ?? ()
#8 0x00000000 in ?? ()
(gdb)

ProblemType: Bug
Architecture: i386
Date: Sat Feb 23 17:27:39 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/firefox-3.0b3/firefox
Package: firefox-3.0 3.0~b3+nobinonly-0ubuntu2
PackageArchitecture: i386
ProcCwd: /home/paerl
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux LG 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux

Tags: apport-bug
Revision history for this message
Pär (parlindhse) wrote :
Revision history for this message
Pär (parlindhse) wrote :

Sorry, this report was intended to be added to #178274, maybe someone who understands this report system can move it there?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.