Closed Bug 303767 Opened 19 years ago Closed 18 years ago

When browsing in a tab, sometimes a new window without toolbars opened

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Version:
1.8 Branch
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 244482

People

(Reporter: bugzilla, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.11) Gecko/20050728 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.11) Gecko/20050728 I have Mozilla open with about 10 tabs. This remains open for days, and I browse several sites in the tabs. Suddenly, when clicking on something in a page, the new content is not loaded in that tab, as it normally is for that site, but a new window opens with the content. This window has no toolbars, scrollbar, etc. and the size of its content pane is exactly the same as in the main browser window. When that window is closed, the browser quits without warning me about open tabs as it would when I close the main window. The tab from where this new window opened is now "dead". It shows the previous content but clicks are not acted upon. When another tab is selected and then this tab, it becomes active but the content is not refreshed (showing the other tab's content). When a link in that new window is clicked, sometimes it closes and content is shown in the correct tab again. It is also possible to get things back to normal again by going back a couple of pages using the dropdown list on the "Go back" button. However, once it has happened it will happen more frequently and also in other tabs, so the browser has to be shutdown and restarted. Reproducible: Sometimes Steps to Reproduce: I have only seen it happen on Linux. (SuSE KDE system) It requires the browser to remain open for longish time (days) and with tabs. Although it is hard to reproduce on demand, I have seen it happen at least a dozen times, with different Mozilla versions, and 2 different SuSE versions.
Version: unspecified → 1.7 Branch
Although version is set to "1.7 Branch" I have seen it happen on older versions and on 1.8a2 as well.
It still happens, occasionally, in SeaMonkey 1.0a Is there really nobody who can confirm this?
What you describe is very unusual. Do you have extensions installed (if so, can you try with a clean install?)? Do you see this with a clean profile?
Version: 1.7 Branch → 1.8 Branch
I have seen it in several versions, each with a clean install. Currently I am running SeaMonkey 1.0a with some plugins but no extensions. (the plugins are SuSE installed: Helix, MozPlugger, DjVuLibre, Java and Flash) My profile is quite old, but I do not want to erase it. What files would be affecting such behaviour? Can I keep prefs.js, bookmarks.html etc, and only delete the .dat and .rdf files?
You don't need to modify your default profile at all. Do this while no instances are currently open: % seamonkey -ProfileManager [create a new profile.] % seamonkey -P new_profile or just invoke normally and the profile selection dialog will appear
I have cleaned out the chrome directory and removed .db .dat and .rdf files, but kept the prefs.js and mail-related directories. While cleaning I found remnants of a previously installed extension "stumbleupon blog", that was no longer appearing in the menus. After this, running seamonkey 1.0b, it has not yet happened again. Will report when it does.
Also seeing this in Firefox 1.5.0.1 on SUSE 9.2 and SUSE 10. Have not seen it in previous Firefox versions (not sure about 1.5.0, but will try). Will also try with clean profile, no extensions etc.
After the profile cleanup I did earlier, I have not seen it happen for a long time... but a few minutes ago it happened again. Browser version is now Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0 OS is SuSE 9.2
Creating and using a new profile did not help (Firefox 1.5.0.1).
Some more info: I'm using KDE and installed Firefox from the official tarballs.
More info with Firefox 2.0b1, SUSE 10.0, KDE 3.4. When that new window opens, the following appears on the terminal where Firefox sends its output: (Gecko:24578): Gdk-WARNING **: GdkWindow 0x3e77722 unexpectedly destroyed (Gecko:24578): Gdk-WARNING **: GdkWindow 0x3e77720 unexpectedly destroyed (Gecko:24578): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `window != NULL' failed (Gecko:24578): Gdk-CRITICAL **: gdk_window_set_back_pixmap: assertion `GDK_IS_WINDOW (window)' failed (Gecko:24578): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:24578): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:24578): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:24578): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:24578): Gdk-CRITICAL **: gdk_window_resize: assertion `GDK_IS_WINDOW (window)' failed Some time later, after some more browsing: (Gecko:24578): Gdk-WARNING **: GdkWindow 0x3e7771c unexpectedly destroyed (Gecko:24578): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `window != NULL' failed (Gecko:24578): Gdk-CRITICAL **: gdk_window_set_back_pixmap: assertion `GDK_IS_WINDOW (window)' failed (Gecko:24578): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:24578): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:24578): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:24578): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:24578): Gdk-CRITICAL **: gdk_window_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:24578): Gdk-CRITICAL **: gdk_window_hide: assertion `GDK_IS_WINDOW (window)' failed (Gecko:24578): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `window != NULL' failed (Gecko:24578): Gdk-CRITICAL **: _gdk_window_destroy_hierarchy: assertion `window != NULL' failed (Gecko:24578): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (Gecko:24578): Gdk-WARNING **: GdkWindow 0x3e777aa unexpectedly destroyed (Gecko:24578): Gdk-WARNING **: GdkWindow 0x3e777d9 unexpectedly destroyed
I have the same exact behaviour in Firefox 1.5.0.7pre on Solaris 9 Additionally, I can close the orphaned frame by closing the tab (where the content is originally suppose to appear, but appeared in the orphaned frame instead). However, once this starts to happen, it happens repeatedly with newly opened tabs as well as older tabs.
Yes, they seem to be more or less duplicates of the same bug, except maybe the first (the one that is talking a lot about iframes, 64-bit etc, all things that are not related to the one I reported). Reading all this, it looks like it is tied to the GTK2 build. I encountered it only on Linux, never on Windows. Others apparently report the same thing on a Sun. Maybe it is related to (blocking) popups, that thought does not seem to be far off. I usually see it when opening "overcrowded" (the makers probably call it "rich") sites, the ones you would also expect to send popups. It could be that the browser is halfway opening a popup, then decides to block it, but leaves the opened window as a default window for the content to be displayed in??
It is in fact a duplicate of bug 244482, which contrary to what the status whiteboard said isn't 64-bit only or iframe-specific. It's all one bug appearing in several ways. *** This bug has been marked as a duplicate of 244482 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
*** This bug has been confirmed by popular vote. ***
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.