I've observed firefox to be rather unstable of late: from time to time, the UI would simply freeze, and I'd have to kill and restart the application. I'd say this is since Firefox 15, but I'm not sure. Today, I encountered this repeatedly. Due to the latest bunch of Java updates and portage fetch restrictions, I had to download various files manually from Oracle. In two out of four cases, I'd experience just such a freeze the moment I click on a link and the "Save as" dialog should appear. Reproducible: Sometimes Steps to Reproduce: 1. Start Firefox 2. Open http://www.oracle.com/technetwork/java/javase/downloads/jre6u37-downloads-1859589.html 3. Accept terms 4. Click on jre-6u37-linux-i586.bin Actual Results: Firefox freezes Expected Results: KDE file chooser dialog box asking me where to save the file For the latest freeze, I had FF started from console, and got this output there: (firefox:29990): GLib-GObject-WARNING **: cannot register existing type `GdkWindow' (firefox:29990): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed (firefox:29990): Gdk-CRITICAL **: gdk_window_get_display: assertion `GDK_IS_WINDOW (window)' failed
Created attachment 327014 [details] emerge --info
What directory is your file dialog trying to open? Now if the answer is DISTDIR, you owe me two internets.
16.0.1 has just been added to tree, if you can duplicate with it please update your report.
(In reply to comment #2) > What directory is your file dialog trying to open? Now if the answer is > DISTDIR, you owe me two internets. Not $DISTDIR, but ~/downloads/java. (In reply to comment #3) > 16.0.1 has just been added to tree, if you can duplicate with it please > update your report. Will do so after my next sync. Will report back the moment I encounter this again. If you don't hear from me within the month, then I assume this issue will have vanished for good.
Just had this
Sorry, wrong button, meant to edit the subject. Had a freeze again in firefox-16.0.2. Not related to file chooser dialog this time. Instead the issue occurred while following a link. ~/.xsession-errors shows the same three error messages described in comment #0.
Had this yet again, this time apparently triggered by launching a second firefox process, which attempts to operate as a remote and open a window in the first. Same error message. Now I've attached gdb to my running firefox, with a breakpoint in g_return_if_fail_warning. With a bit of luck, that will get me a backtrace for the g_once_init_leave assertion at least. Reproducing this thing is still a problem.
Created attachment 329040 [details] backtrace from g_return_if_fail_warning (In reply to comment #7) > Now I've attached gdb to my running firefox, with a breakpoint in > g_return_if_fail_warning. Here is a backtrace from when g_return_if_fail_warning got called. This happens two times, for the two critical assertion errors, and the attachment covers both. This time, Dropbox might have been involved in triggering this: I used the Dropbox tray icon to open the Dropbox website, which opened a new firefox tab. I guess I might have activated a different firefox window first, and when I eventually got to the Dropbox tab, things froze. At least that's how I remember it, but I might have mixed things up in my memory.
Yet again, this time perhaps triffered by mozplugger embedding an okular window to view some pdf.
I can confirm the same as in #7: as soon as I try to open a second instance of firefox, the first one freezes forever with the same gdk messages. This is even 100% reproducible with all plugins and addons disabled, as well as starting "firefox -safe-mode". [www-client/firefox-19.0.2 / arch=i686]
Update: this only seems to happen when starting firefox via KDE (shortcut), and *not* when starting from a xterm/konsole window. Also reproducible when starting with a new user profile (removing ~/.mozilla). Workaround: edit the properties of the shortcut and activate "start in shell" (found here: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1085972 comment #2)
If you can reproduce with 31.3.0 from mozilla overlay please re-open. Please update bug info completely if reopened to ensure we via it.
