Closed Bug 997901 Opened 10 years ago Closed 6 years ago

crash if master password requested before main window complete

Categories

(Core :: Widget: Gtk, defect)

28 Branch
x86_64
Linux
defect
Not set
critical

Tracking

()

RESOLVED WONTFIX

People

(Reporter: david+bugs, Unassigned)

References

Details

(Keywords: crash, crashreportid, reproducible)

Crash Data

(First, I'm sorry if this bug report is a bit vague, I wasn't able to narrow the bug as much as I wanted.)

It seems that, when Firefox is running on a machine that is too slow and has too many extensions installed, the master password (requested for Firefox sync) is asked before the main window is "ready" and this causes a crash.

I was able to reproduce this with the Ubuntu-packaged Firefox 28.0+build2-0ubuntu0.12.10.1 on Ubuntu 12.10 as follows:

* use a sufficiently slow machine (in my case, an AMD C-70),

* start with a pristine profile,

* install the Adblock Plus (2.5.1) and Greasemonkey (1.15) extensions,

* set up a master password and a Firefox sync account (so that the master password will be asked at start).

The "password required" window appears requesting the master password, and sometimes the main window starts to appear, but before it appears competely, Firefox crashes.

I strongly suspect that this is not related either to Adblock Plus or to Greasemonkey but simply to the fact that they slow down Firefox at startup (removing one of the extensions causes the master password to be prompted only after the main window is ready, and Firefox does not crash).  Maybe the fact that I'm using Compiz also comes in play.

Here are the messages upon crashing:

** (firefox:17573): WARNING **: Failed to open webapp application path dir /usr/share/gnome-classic/unity-webapps/userscripts: Error opening directory '/usr/share/gnome-classic/unity-webapps/userscripts': No such file or directory

** (firefox:17573): WARNING **: Failed to open webapp application path dir /usr/share/gnome/unity-webapps/userscripts: Error opening directory '/usr/share/gnome/unity-webapps/userscripts': No such file or directory

** (firefox:17573): WARNING **: Failed to open webapp application path dir /usr/local/share/unity-webapps/userscripts: Error opening directory '/usr/local/share/unity-webapps/userscripts': No such file or directory

(firefox:17573): Gdk-CRITICAL **: gdk_keymap_have_bidi_layouts: assertion `GDK_IS_KEYMAP (keymap)' failed

(firefox:17573): GLib-GObject-WARNING **: cannot register existing type `GdkKeymap'

(firefox:17573): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

(firefox:17573): GLib-GObject-CRITICAL **: g_type_register_static: assertion `parent_type > 0' failed

(firefox:17573): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
Segmentation fault (core dumped)

Once I have a bug number, I'll send a crash report with the bug number as a comment.
I sent a crash report with the comment "See bug #997901".  In case it helps forensics, the Firefox profile for the crash is at http://www.madore.org/~david/.tmp/firefox-bug-997901.tar.gz (this was a pristine profile, only the steps described in the bug report were applied: install Adblock Plus and Greasemonkey, and a dummy Firefox sync account).
It looks like this is your crash report: bp-09e74426-4aec-4239-b4d9-dcee02140417
so it's likely a dupe of bug 846863.

Thanks for the detailed steps to reproduce - hopefully we can finally fix this now.
Blocks: 846863
Severity: normal → critical
Component: General → Widget: Gtk
Product: Firefox → Core
Crash Signature: [@ IA__gdk_keymap_get_for_display ]
Yes, libgtk-3.0 is loaded in the report of comment 2, so same fundamental problem as bug 846863.

https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1138473 says fixes have been released, but I don't understand which branches have the fixes.

Uninstalling libunity-webapps should fix it.
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Closing because no crash reported since 12 weeks.
You need to log in before you can comment on or make changes to this bug.