Comment 57 for bug 226470

Yes, that version is the Firefox 2.0 version. As such it is old. I have not yet been able to get the 3.0 version to assemble in the same way. But given the history of this problem I think it is present in most if not all versions of Linux based Firefox. You can attach firefox-bin in gdb and set a breakpoint at "g_log_default_handler" and that is the initial entry point for all subsequent errors. Under "normal" operations, Firefox should never be posting GDK/GLIB errors. The problem (IMO) is that the g_log_default_handler is an upper level reporting function. What we really need to get our hands on is the DestroyNotify condition which is occuring at a much lower level. I believe that this is being driven either by (a) a much higher misuse of the gdk code (as some discussion) seems to indicate; or (b) a much lower level problem in the gdk and threads usage.

But it seems apparent at this point that it is Linux/GTK specific problem so we are not going to receive assistance from Firefox developers focused on other operating systems.