Extension crashes in Firefox when trying to autofill

francislavoie

When trying to autofill from the login form, nothing happens, and then when I click on the extension button in the top-right tray, it asks me to log in again.

It works fine though, when clicking the Autofill button from the extension panel.

I assume this means the extension's background worker crashed when it received a post message from the in-page worker. I don't know how to find the console for extensions in Firefox (I did build an extension for Chrome years ago, haven't played with them since), otherwise I would post logs. How do I find it?

---

1Password Version: Not Provided
Extension Version: 2.4.6
OS Version: Ubuntu 21.04
Browser:_ Firefox Dev Edition 106.0b9

francislavoie

Well, I managed to open the Browser Console and when trying to do the autofill, I see this error:

10:20:10.858 AbortError: Actor 'Conduits' destroyed before query 'RuntimeMessage' was resolved ConduitsParent.jsm:362
    _raceResponses resource://gre/modules/ConduitsParent.jsm:362

francislavoie

Ah, when clicking the Multiprocess mode in the Browser Console, I get more stuff.

At :15 is when I clicked on the login form to show the pop-over with the login options, and at second :16 is when I clicked on the item I wanted to fill with. Notice the blue message, it locked 1Password after crashing it looks like.

steph.giles

Hey @francislavoie,

Thanks for providing all of this information. Can you let me know if you have the 1Password desktop app installed?

francislavoie

I do have it installed, but it never worked with Firefox Developer edition because it uses a different process/location than the regular Firefox.

This all used to work until sometime last week I think. I was chalking it up to just getting a buggy extension update and was waiting for a fix since I figured it seems like a pretty major problem and is probably happening for everyone, but I guess not 😅 so here I am now

steph.giles

Thanks for getting back to me @francislavoie,

Can you try the steps below and let me know if the same behaviour occurs:

1. Right click the 1Password icon in your browser toolbar and choose 'Settings'
2. Disable the setting that says 'Integrate with 1Password app'

Let me know how you get on!

francislavoie

Okay, did that, turned off app integration.

Tried a login again, the logs are quieter, but still crashes.

steph.giles

Thank you for the prompt response @francislavoie.

At this point, I think it would be useful if we could take a closer look at some logs and what may be going wrong. Can you possibly send over the console log from your browser as well as a diagnostics report from your computer:

• Save a console log for 1Password in your browser
• How to send a 1Password diagnostics report

Please attach the reports to an email message addressed to support+forum@1password.com with a link to this thread.

You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!

francislavoie

Aha, that's where the inspector is in Firefox. That's what I was looking for.

This is all there is in the logs immediately after selecting an item from the form popup/overlay. It causes the extension to crash and the vault to lock itself.

05:05:44.661 [OP] Locked at Thu Oct 13 2022 05:05:44 GMT-0400 (Eastern Daylight Saving Time) background.js:2:2282242
05:05:44.681 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    Ai moz-extension://0831b45a-2104-422a-a4fb-4ec2b078b545/background/background.js:2
background.js:2:1060123
    Ai moz-extension://0831b45a-2104-422a-a4fb-4ec2b078b545/background/background.js:2
    AsyncFunctionThrow self-hosted:811
    (Async: async)
    Xye moz-extension://0831b45a-2104-422a-a4fb-4ec2b078b545/background/background.js:2
    InterpretGeneratorResume self-hosted:1819
    AsyncFunctionNext self-hosted:807
    (Async: async)
    Ude moz-extension://0831b45a-2104-422a-a4fb-4ec2b078b545/background/background.js:2
    Dde moz-extension://0831b45a-2104-422a-a4fb-4ec2b078b545/background/background.js:2
    AsyncFunctionNext self-hosted:807
    (Async: async)
    xde moz-extension://0831b45a-2104-422a-a4fb-4ec2b078b545/background/background.js:2
    InterpretGeneratorResume self-hosted:1819
    AsyncFunctionNext self-hosted:807
    (Async: async)
    kye moz-extension://0831b45a-2104-422a-a4fb-4ec2b078b545/background/background.js:2
    kye moz-extension://0831b45a-2104-422a-a4fb-4ec2b078b545/background/background.js:2
    action moz-extension://0831b45a-2104-422a-a4fb-4ec2b078b545/background/background.js:2
    Vse moz-extension://0831b45a-2104-422a-a4fb-4ec2b078b545/background/background.js:2
    r moz-extension://0831b45a-2104-422a-a4fb-4ec2b078b545/background/background.js:2
    apply self-hosted:2736
    raw resource://gre/modules/ExtensionCommon.jsm:2519
    wrapResponse resource://gre/modules/ExtensionChild.jsm:225
    responses resource://gre/modules/ExtensionChild.jsm:194
    map self-hosted:221
    emit resource://gre/modules/ExtensionChild.jsm:194
    recvRuntimeMessage resource://gre/modules/ExtensionChild.jsm:376
    recvRuntimeMessage self-hosted:1356
    _recv resource://gre/modules/ConduitsChild.jsm:82
    receiveMessage resource://gre/modules/ConduitsChild.jsm:188

As for the "diagnostic report", that seems to be only for apps, not the browser extension. I don't see any option in the extension's settings to generate a report.

Should I still send a support email? I didn't because there's nothing sensitive in these logs, so I figured I can just post it here.

steph.giles

That's interesting @francislavoie that you say 1Password locks when you click on the inline menu. We have recently come across a small bug in the latest Beta which I think you may be encountering, I'm sorry I didn't come to this conclusion sooner!

Can you try uninstalling 1Password in your browser completely and reinstalling a fresh copy from here and let me know if it improves things?

francislavoie

Yeah, that build fixes it! Thanks :)

steph.giles

Thank you for getting back to me! I'm glad things are working as they should be.