295943 - Problem with unoccupied GtkSocket

Status: RESOLVED INVALID

(Core Graveyard :: Embedding: GTK Widget, defect)

Description

[Braden]

This bug was introduced between Firefox 1.0.2 and 1.0.3. Or at the very least,
it morphed into something nastier at that time.

I have plug-in, most of which runs in a separate process. My actual plug-in
shared object creates a GtkSocket, then launches a separate process that uses a
GtkPlug. If the attempt to launch the subprocess fails (e.g., the executable
cannot be found), things fall apart in the browser. Messages like this are
produced; and the browser is unstable and soon crashes:

Xlib: unexpected async reply (sequence 0x35ad)!
Xlib: unexpected async reply (sequence 0x35ae)!
Xlib: sequence lost (0x10000 > 0x35d8) in reply type 0x0!
The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 13787 error_code 2 request_code 2 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.)
Xlib: sequence lost (0x10000 > 0x35e3) in reply type 0x0!
Xlib: sequence lost (0x10460 > 0x35e3) in reply type 0x65!

Firefox 1.0.3 and 1.0.4 produces messages of the above form. Firefox 1.0.2 does
something a bit different:

*** glibc detected *** double free or corruption (out): 0x0902d2d0 ***

While this sounds ominous, the browser does not appear to be made unstable by this.

Comment 1

[Braden]

The summary "Problem with unoccupied GtkSocket" might be off the mark. It's just
a naive guess because I couldn't think of how else to succinctly describe this
issue.

Comment 2

[Braden]

Nevermind. This was me not shutting down my forked process appropriately.