Closed
Bug 1483490
Opened 6 years ago
Closed 6 years ago
NS_ERROR_NOT_INITIALIZED
Categories
(WebExtensions :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1408446
People
(Reporter: santiaguzz, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180704194937
Steps to reproduce:
I'm building a new addon for Firefox, however I'm using the latest API for WebExtensions . I recently published the first version of my addon and it seems to work fine in GNU/Linux distributions. If I try to install it on a Windows machine it will run fine if the options page is opened before any other facility, particularly, if I try to open an editor before my options page is opened next error will arise:
NS_ERROR_NOT_INITIALIZED : ext-windows.js:16
My editors are opened in a new window created with "browser.windows.create", so, as mentioned above any component necessary must be created by the API as far as I know, is there any way I can force this initialization for created windows?
Extension name: JSloader : https://github.com/szz-dvl/JSLoader
Thanks ins advance.
Actual results:
The tab inside the new window crash, and all the extension stop working after that.
Expected results:
The editor must show in a new created window.
Reporter | ||
Updated•6 years ago
|
Product: Firefox → WebExtensions
Reporter | ||
Comment 1•6 years ago
|
||
It seems that it does depends on the OS, as it seems if the option page is not opened before any new window created with "browser.windows.create" the extension will crash in some old windows versions.
Comment 2•6 years ago
|
||
I cannot reproduce the issue on Ubuntu 16.04, but I will not close it because I am not 100% sure that there doesn't exist another way to Load the Extension.
I think setting WebExtensions :: General component will be a good stating point.
Component: Untriaged → General
Comment 3•6 years ago
|
||
Your extension is too complex for us to diagnose the series of bugs you are submitting. You need to provide us with a minimal test case extension that reproduces the problem.
Flags: needinfo?(santiaguzz)
Reporter | ||
Comment 4•6 years ago
|
||
I wrote minimal extension providing an example of what is happening. When you pres Alt+Shift+W a new window with a Welcome title must open, however windows are blank until you resize them. The error is showing a little after the window is opened from (unknown):
[Exception... "Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMessageSender.sendAsyncMessage]" nsresult: "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)" location: "JS frame :: resource://gre/modules/ExtensionUtils.jsm :: sendAsyncMessage :: line 524" data: no] (unknown)
sendAsyncMessage resource://gre/modules/ExtensionUtils.jsm:524:51
_handleMessage/deferred.promise< resource://gre/modules/MessageChannel.jsm:985:9
I can see another one which always shows:
TypeError: cannot use 'in' operator to search for 'canGoBack' in 'browser' tabbrowser.xml:2473:1
The extension can be found at: https://github.com/szz-dvl/example_minimal
Thanks in advance.
Flags: needinfo?(santiaguzz)
Updated•6 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•