Context Menu X options freezes Firefox




Extension Compatibility
2 years ago
2 years ago


(Reporter: quality+bugzilla, Unassigned)



43 Branch

Firefox Tracking Flags

(Not tracked)




2 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20151208100201

Steps to reproduce:

1. Install Firefox 43
2. Install Context Menu X extension version from
3. Open Addons Manager
4. Select Options for that extension

Actual results:

Firefox completely freezes.

Expected results:

Firefox should never freeze.


2 years ago
Severity: normal → major
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64


2 years ago
Severity: major → critical
Component: Untriaged → Extension Compatibility
Ever confirmed: true
Keywords: hang
OS: Windows 7 → All
Hardware: x86_64 → All
Summary: Firefox completely FREEZES when accessing Options of specific extension → Context Menu X options freezes Firefox
I couldn't reproduce on Mac OS (nothing happens when I click on the button), but I've notified the developer about this bug.

Comment 2

2 years ago
What's happening is that there is no longer a preferences XUL at chrome://browser/content/browser.xul , so an empty(?) window pops up which absorbs all the mouse clicks for that window. It is not a full freeze, as keyboard shortcuts work, and one can open a new window with Ctrl-N and then select File > Exit to quit. That said, I will get it solved, of course.

Comment 3

2 years ago
Sorry I meant chrome://browser/content/search/engineManager.xul .

Comment 5

2 years ago
Question: So far, we have concluded that this a bug in an extension, but the effect is the appearance of Firefox freezing.

The extension author will be fixing the extension, but does Firefox require a patch to prevent this type of apparent freeze?

Comment 6

2 years ago
Based on my past experience (bug 1189434), I guess Firefox team will not make a shim, if it does not have a broad impact known. Feel free to comment this point, if I made a mistake.

Comment 7

2 years ago
I think I fixed this with the latest version.
You need to log in before you can comment on or make changes to this bug.