Error in Firefox Extension

pento

The Firefox extension currently seems to be crashing when it starts, opening the extension debugger shows the following console messages repeating over and over:

[Exception... "Component not initialized"  nsresult: "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)"  location: "JS frame :: resource://gre/modules/ExtensionChild.jsm :: api/register/publicAPI.onDisconnect< :: line 266"  data: no]
api/register/publicAPI.onDisconnect<@resource://gre/modules/ExtensionChild.jsm:266:42
listener@resource://gre/modules/ExtensionChild.jsm:323:17
disconnectByOtherEnd@resource://gre/modules/ExtensionChild.jsm:404:15
receiveMessage@resource://gre/modules/ExtensionChild.jsm:232:44
_handleMessage/</<@resource://gre/modules/MessageChannel.jsm:962:27
_handleMessage/<@resource://gre/modules/MessageChannel.jsm:961:9
_handleMessage@resource://gre/modules/MessageChannel.jsm:959:16
receiveMessage/<@resource://gre/modules/MessageChannel.jsm:225:14
receiveMessage@resource://gre/modules/MessageChannel.jsm:218:10
MessageChannel.jsm:964
    _handleMessage resource://gre/modules/MessageChannel.jsm:964
[CHROME:NM] Port <[object Object]> disconnected: No disconnect message global.min.js:249:130
[AGENT] Connection [object NativeMessagingConnection] disconnected. global.min.js:105:465
Finished loading auth configuration. Processing callbacks. global.min.js:88:471

This error also occasionally pops up:

Error processing windowTypes: This property is deprecated global.min.js:250
    makeError resource://gre/modules/Schemas.jsm:493
    logDeprecation resource://gre/modules/Schemas.jsm:1189
    checkDeprecated resource://gre/modules/Schemas.jsm:1201
    normalizeBase resource://gre/modules/Schemas.jsm:1324
    normalize resource://gre/modules/Schemas.jsm:2155
    r resource://gre/modules/Schemas.jsm:1849
    withPath resource://gre/modules/Schemas.jsm:578
    checkProperty resource://gre/modules/Schemas.jsm:1848
    normalize resource://gre/modules/Schemas.jsm:1921
    normalize resource://gre/modules/Schemas.jsm:1457
    fixedArgs resource://gre/modules/Schemas.jsm:2518
    map self-hosted:291
    checkParameters resource://gre/modules/Schemas.jsm:2513
    stub resource://gre/modules/Schemas.jsm:2619
    a moz-extension://{1password extension internal UUID}/global.min.js:250
    apply self-hosted:2018
    applySafeWithoutClone resource://gre/modules/ExtensionCommon.jsm:595
    fire resource://gre/modules/ExtensionChild.jsm:1232
    receiveMessage resource://gre/modules/ExtensionChild.jsm:1236
    _callHandlers resource://gre/modules/MessageChannel.jsm:914
    _callHandlers resource://gre/modules/MessageChannel.jsm:913
    promise resource://gre/modules/MessageChannel.jsm:992
    _handleMessage resource://gre/modules/MessageChannel.jsm:989
    _handleMessage self-hosted:1021
    receiveMessage resource://gre/modules/MessageChannel.jsm:225
    forEach self-hosted:266
    receiveMessage resource://gre/modules/MessageChannel.jsm:218

I'm using Firefox 70.0.1, restarting Firefox and 1Password doesn't seem to help.

---

1Password Version: 7.4.2.BETA-0 (70402000)
Extension Version: 4.7.5.90
OS Version: macOS 10.15.1
Sync Type: 1Password.com

ag_yaron

Hey @pento ,
There are Three things I'd like to test (in that particular order) to try and understand where is the issue coming from:
1. Disable all other extensions except for 1Password and see if it works properly.
2. Create a new Firefox user profile and install only the 1Password extension there: https://1password.com/browsers/firefox/ - see if it works there.
3. Restart your Mac in Safe Mode by holding SHIFT as soon as you hear the Mac's restart chime, then launch and unlock 1Password, launch Firefox see if it works without crashing there.

Let me know at which point were you able to get a functioning extension, if any.

pento

Thanks for the suggestions, @Yaron.

1 and 2 didn't work, but 3 did. Interestingly, after then rebooting back to normal mode, it continued to work properly, sooo... 🤷🏻‍♂️ Not sure what changed, but it seems to work now!

AGAlumB

Ah interesting. Thanks for the update! It sounds like either something was just temporarily hung up in Firefox that the reboot cleared up, or something was misconfigured and it was able to right it. Anyway, it sounds like you should be all set, but we're here if you need us. :)