firefox crashed

Bug #116189 reported by Timo Aaltonen on 2007-05-22
8
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Medium
Unassigned

Bug Description

... [Feisty] Crash: 'BadIDChoice (invalid resource ID chosen for this connection)'

Happened to be running firefox from the terminal, so I caught this when it crashed all of a sudden:

DOUBLE-CLICK: 400 --> -1 THRESHOLD: 8 --> -1 The program 'Gecko' 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 100181746 error_code 14 request_code 155 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.)

Thank you Timo Aaltonen for submitting this report.

Could you please try to obtain a backtrace by following the instructions on
[1], or upload the crash report that probably was generated during the crash
and that should be located at /var/crash/ to [2].

Please indicate which extensions/plugins do you have enabled; and if this crash
is reproducible describe the steps that lead to it (it is very important for us
to have a test case for each crash).

This will greatly aid us in tracking down your problem.

Thanks in advance.

H. Montoliu

[1] https://wiki.ubuntu.com/MozillaTeam/Bugs
[2] https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/116189/+addcomment

description: updated
Changed in firefox:
assignee: nobody → hmontoliu
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Changed in firefox:
assignee: hmontoliu → mozilla-bugs

Thank you for the bug report however this report lacks information we need to investigate it further. For this reason, we are now going to close the bug - please feel free to reopen when you have more information at hand.

Further information can be found at [1].

[1] https://wiki.ubuntu.com/MozillaTeam/Bugs

Changed in firefox:
status: Needs Info → Rejected

Just received the same on Debian sid FWIW. x86-64 when I pasted a link into the browser (to open a new window).

I've noticed this happening a fair bit - I wonder if perhaps gnash (cvs20070512.1554-1) is partly to blame. .xsession-errors:

xEmbed supported in this Mozilla version
Gtk2+ supported in this Mozilla version
NewStream: The full URL is http://www.yolinux.com/AWEBDAP/aWebDapMovie1.swf
Closed 77files.Forked sucessfully, child process PID is 12351

Starting process: /usr/bin/gnash -v -x 33229104 -j 500 -k 325 -u http://www.yoli
nux.com/AWEBDAP/aWebDapMovie1.swf -U http://www.yolinux.com/AWEBDAP/index.html -
P bgcolor=#CCCCCC -P height=325 -P pluginspage=http://www.macromedia.com/shockwa
ve/download/index.cgi?P1_Prod_Version=ShockwaveFlash -P quality=autohigh -P src=
aWebDapMovie1.swf -P type=application/x-shockwave-flash -P width=500 -
Verbose output turned on
Setting width to 500
Setting height to 325
Setting root URL to http://www.yolinux.com/AWEBDAP/aWebDapMovie1.swf
Setting base URL to http://www.yolinux.com/AWEBDAP/index.html
No rendering flags specified, using rcfile
virtual bool gnash::GtkGui::init(int, char***) enter
12:51:46: Created XEmbedded window
virtual bool gnash::GtkGui::createMenu() enter
virtual bool gnash::GtkGui::setupEvents() enter
static gboolean gnash::GtkGui::realize_event(GtkWidget*, GdkEvent*, void*) enter
framebuffer pixel format is RGB24
Base url set to: http://www.yolinux.com/AWEBDAP/index.html
virtual bool gnash::GtkGui::createWindow(int, int) enter
GTK-AGG: 510000 bytes offscreen buffer allocated

initialized AGG buffer <0x2afa5c1e5010>, 510000 bytes, 500x325, rowsize is 1500
bytes
virtual bool gnash::GtkGui::run() enter
Corrupt JPEG data: premature end of data segment
Child process exited with status 15
.....
The program 'gecko' 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 43142266 error_code 14 request_code 157 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've not had this now for a little while FWIW (running Intrepid on laptop (64bit)) and Debian unstable on desktop (also 64bit, using flash 10 beta).

Alexander Sack (asac) on 2008-12-16
Changed in firefox:
assignee: mozilla-bugs → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers