GNOME Bugzilla – Bug 352408
Opens link in new window without UI, crashes
Last modified: 2007-03-14 14:44:23 UTC
Steps to reproduce: 1. Use epiphany for a while until it opens a link in a new window without any menu or tool bars. (The frequency with which this occurs seems to be arbitrary; though "busy" Web pages with lots of content manipulation via scripting seem to increase the likelihood.) 2. Close the oddball window. 3. Crash. Stack trace: Other information:
Can you please give the URL of the page that opened the menuless window that lead to the crash?
As far as I can tell, it is completely and utterly random. It happens sometimes when clicking links on cnn.com; but that's just because it's one of the sites I visit regularly. It seems to happen no matter where I am browsing. I have attached gdb to my current browser instance. Hopefully I can provide a stack trace in the next few days.
The odd window/crash happened again while I had gdb attached to the process. But I didn't get a stack. All I got was Program exited with code 01. Certainly epiphany *thinks* it crashed when I start it back up again. Any suggestions for how I could provide useful feedback on this would be appreciated.
Braden, does this still happen in Ephy 2.16?
Yes.
Braden, did you install debug packages for epiphany, glib/gtk and mozilla? Is there any specific URL where this happens often?
Gecko bug https://bugzilla.mozilla.org/show_bug.cgi?id=263160 .
(In reply to comment #6) > Braden, did you install debug packages for epiphany, glib/gtk and mozilla? I have not. I can do so; but then what's the next step? This crash is yielding no stack. (See comment #3.) > Is there any specific URL where this happens often? I typically leave Epiphany open for long periods. If cnn.com is loaded in a window, it can tend to happen because cnn.com triggers a reload after several minutes. (In reply to comment #7) > Gecko bug https://bugzilla.mozilla.org/show_bug.cgi?id=263160 . Interesting. The similarities are striking enough that there's reason to suspect this may be a slightly different manifestation of the same bug; but the symptoms are not quite identical. Whereas this Gecko bug describes a window that will not be redrawn correctly, the rogue Epiphany windows I'm observing don't have this problem.
*** Bug 417973 has been marked as a duplicate of this bug. ***
I agree that 417973 is a duplicate of 352408. There are 2 aspects of the core bug both of which involve gtk+. The first, as documented under Mozilla/Firefox bug #263160 the problem first springs to light when one gets a "GdkWindow 0x####### unexpectedly destroyed" error. This is due to a DestroyNotify condition arriving from gdkevents-x11.c. It is unknown currently what is generating the DestroyNotify condition. The problem may be due to the setup of windows and tabs which apparently takes place in nsWindow.cpp. If epiphany uses nsWindow.cpp to setup its windows (or similar code) then the problem is likely to occur in epiphany as well. As recently documented under 263160, the problem can also be generated by gmail under SeaMonkey. Gmail is presumably using Javascript to generate and manipulate windows. So the problem is with the gtk+ libraries and how they manipulate windows and not particularly with any browser. It is my personal opinion there there is some kind of concurrency or thread problem in gtk as the problem only seems to occur when a system is under high CPU and/or network loads. The second problem, and by some arguments the more severe, is that *if* one closes one of these popup windows it causes a fatal X error and aborts the browser session entirely. This problem really needs the attention of someone who understands how gtk+ is supposed to work and/or how threads may cause problems in gtk+.
The status on this bug should be changed. If I can produce the bug in SeaMonkey using gmail, it is highly likely I can produce it in epiphany using gmail. It is correct that it is not an epiphany bug per se, but it is a GTK bug (feature?) and it is definitely NOT resolved.
As documented under Bug #417973, the extensive documentation for this is in the Mozilla bug database: https://bugzilla.mozilla.org/show_bug.cgi?id=263160
This bug has been resubmitted as: http://bugzilla.gnome.org/show_bug.cgi?id=418199