[MASTER] firefox-3.0b5 received an X Window System error: 'BadIDChoice'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mozilla Firefox |
Fix Released
|
Medium
|
|||
libxcb |
Fix Released
|
Medium
|
|||
firefox-3.0 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
Jaunty |
Invalid
|
Undecided
|
Unassigned | ||
gtk-qt-engine (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
Jaunty |
Invalid
|
Undecided
|
Unassigned | ||
libxcb (Ubuntu) |
Fix Released
|
Medium
|
Alexander Sack | ||
Hardy |
Won't Fix
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Medium
|
Alexander Sack |
Bug Description
Binary package hint: firefox-3.0
Starting a few days ago, maybe a week or so, FF3 started crashing randomly,
after 1h or so, usually when there are tens of windows and tabs open. It
probably happened after some update of the X server, come to think of it.
Calling it from a terminal and not from the window manager yields the following
trace:
The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
(Details: serial 73442980 error_code 14 request_code 153 minor_code 4)
(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.)
I am not sure what to do with that? Is firefox the program I should run with
the --sync command line option?
Relevant packages (hardy up-to-date):
ii xserver-xorg 1:7.3+10ubuntu10 the X.Org X server
ii xserver-xorg-core 2:1.4.1~
ii kdm-kde4 4:4.0.3-0ubuntu2 X display manager for KDE 4
ii firefox-3.0 3.0~b5+
Tell me what to do to help you investigate this issue.
Changed in firefox: | |
status: | Unknown → Confirmed |
Changed in firefox: | |
status: | Confirmed → Invalid |
Changed in firefox: | |
status: | Invalid → Unknown |
Changed in firefox: | |
status: | Unknown → Confirmed |
Changed in gtk-qt-engine: | |
status: | New → Incomplete |
summary: |
- firefox-3.0b5 received an X Window System error: 'BadIDChoice' + [MASTER] firefox-3.0b5 received an X Window System error: 'BadIDChoice' |
Changed in libxcb: | |
importance: | Undecided → Unknown |
status: | New → Unknown |
Changed in libxcb (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in gtk-qt-engine (Ubuntu): | |
status: | Incomplete → Invalid |
Changed in firefox-3.0 (Ubuntu): | |
status: | Triaged → Invalid |
Changed in libxcb: | |
status: | Unknown → Confirmed |
Changed in libxcb: | |
status: | Confirmed → Fix Released |
Changed in firefox: | |
status: | Confirmed → Fix Released |
tags: |
added: verification-done removed: verification-needed |
Changed in libxcb: | |
importance: | Unknown → Medium |
Changed in firefox: | |
importance: | Unknown → Medium |
Changed in libxcb: | |
importance: | Medium → Unknown |
Changed in libxcb: | |
importance: | Unknown → Medium |
Update. No core file is produced, and running firefox under gdb gives nothing. The "apt-cache search firefox debug" command does not show any package related to firefox-3.
The problem reproduces fairly regularly. Example of a gdb session:
$ ulimit -c firefox- 3.0b5/firefox firefox- 3.0b5/firefox. ..(no debugging symbols found)...done.
10000
$ gdb
[...]
(gdb) file /usr/lib/
Reading symbols from /usr/lib/
(gdb) break gdk_x_error
Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (gdk_x_error) pending.
(gdb) run --sync
[...]
[New Thread 0x40c5d950 (LWP 24772)]
[Thread 0x40c5d950 (LWP 24772) exited]
[New Thread 0x40c5d950 (LWP 24773)]
The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
(Details: serial 147095966 error_code 14 request_code 153 minor_code 4)
(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.)
Program exited with code 01.
(gdb) quit
I'm still confused as to what I could or should do to help pin down the source of the trouble.