484997 - Seg fault on linux

Status: RESOLVED DUPLICATE of bug 458092

(Core :: General, defect)

Description

[David Dahl :ddahl]

Crash - no crash reporter started up.

This happened to my nightly Shiretoko build this morning one time:



(firefox-bin:7408): Gdk-CRITICAL **: gdk_pixmap_new: assertion `(width != 0) && (height != 0)' failed
Tab selected.
Tab selected.
2009-03-24 08:54:23    Engine.Tabs          ERROR    Could not process incoming record: tabChild is undefined (module:tabs.js:229 :: TypeError)
Tab selected.
The program 'firefox-bin' 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 16945070 error_code 14 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.)
Segmentation fault

Comment 1

[Karl Tomlinson (:karlt)]

Thanks for the report.

The BadIDChoice is a libxcb problem https://bugs.freedesktop.org/show_bug.cgi?id=20254, also tracked bug 458092.

The gdk_pixmap_new assertion would be unrelated, but we'd need steps to reproduce or a backtrace from a breakpoint in g_log to know what caused it.

Normally the program exits after BadIDChoice.  The segmentation fault is possibly the program trying to continue, but that is going to be difficult after a BadIDChoice error.

I'll mark this a dup of 458092, as that is the fatal error here.