GNOME Bugzilla – Bug 417973
Current gtk+ gnome libraries cause Firefox/Seamonkey to misbehave.
Last modified: 2007-03-13 20:41:52 UTC
Please describe the problem: Firefox/Seamonkey/Mozilla systems will enter a state where the windows system (i.e. gtk+) will not perform reliably. This is documented extensively under: https://bugzilla.mozilla.org/show_bug.cgi?id=263160 Intervention is needed as to whether this is a Gnome/GTK+ bug (with respect to thread handling) or whether the Mozilla package (Firefox, Seamonkey, etc.) is misusing GTK+ functions. Steps to reproduce: 1. Read the Mozilla bugzilla # 263160. If you push the envelope you will get the conditions. Actual results: One gets a number of popup windows from the windows management system which should not occur. Expected results: One gets windows behavior as windows behavior should be (i.e. no unexpected popups). Does this happen every time? No, it only happens when the system is under high CPU and/or network traffic conditions. It is a resource contention problem. Other information: See the Mozilla bug 263160. There is ample commentary there.
An abort of a gnome window (i.e. the unspawned windows under this bug should never cause an abort of associated process (i.e. a termination of all Netscape/Mozilla associated windows). At most such should cause the termination of the current windoww. Any other terminations fall into the political realm.
This is not an Epiphany bug, and besides, this problem was files previously as bug 352408. If you are requesting comments from Epiphany developers please post to the Epiphany mailing list. Thanks! *** This bug has been marked as a duplicate of 352408 ***