Mac - Chrome Extension Keeps Crashing

Options
WEMasters
WEMasters
Community Member
edited February 10 in 1Password in the Browser

I have deleted and reloaded - still crashes.
I have cleared my cache, rebooted - still crashes

1Password Version: 8.10.24
Extension Version: 1.20.0
OS Version: macos 14.3.1
Browser: Chrome

Comments

  • Dave_1P
    Dave_1P
    Options

    Hello @WEMasters! 👋

    I'm sorry that 1Password is crashing in Chrome on your Mac. Can you tell me a little more about what you mean by "crashing"? Are you seeing a specific screen or error message? If you are then can you post a screenshot of that screen or message?

    You also wrote that you're using version 1.20.0 of the extension. Is this a typo and are you using 2.20.0, which is the latest version?

    I look forward to hearing from you.

    -Dave

  • WEMasters
    WEMasters
    Community Member
    Options

    First the Extension is ON but it's not show in my browser.

  • WEMasters
    WEMasters
    Community Member
    Options

    I can't get a screen shot of the notification that the extension crashes.

  • WEMasters
    WEMasters
    Community Member
    Options

    Now I got it

  • Dave_1P
    Dave_1P
    Options

    @WEMasters

    Thank you for the screenshots. So that we can investigate this further, I'd like to ask for a console log from your end:

    Attach the file to an email message addressed to support+forum@1password.com.

    With your email please include:

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

    -Dave

  • WEMasters
    WEMasters
    Community Member
    Options

    This is all I get

  • WEMasters
    WEMasters
    Community Member
    Options

    And now it's working again.

    IDK what happened, but it's working again.

  • indyhsu
    indyhsu
    Community Member
    Options

    I have the same problem. When the DevTools window is opened, it won't crash. Close the window will crash again.

  • EvonG1P
    EvonG1P
    Options

    Hey there @WEMasters, @indyhsu. I'm sorry to hear about the trouble.

    May I ask which version of Chrome is installed on your device?

    1. Open Chrome.
    2. Paste chrome://settings/help into the address bar and press the Enter key.

    For reference, the current most up to date version of Chrome on Mac is 121.0.6167.160.

    I look forward to hearing back from you.

    -Evon

  • WEMasters
    WEMasters
    Community Member
    Options

    109.0.5414.119

    And it's crashing again so I'm going to try to get that log for you later today.

  • WEMasters
    WEMasters
    Community Member
    Options

    Ok, so I have a bad version of Chrome. The update didn't go well so I have to uninstall and get latest version. We are so programmed to just assume apps are updated automatically. I'll report back after I reinstall Chrome and let you know how it goes.

  • WEMasters
    WEMasters
    Community Member
    Options

    It's working. Sorry for the trouble. The older I get the less I understand how all this works.

  • EvonG1P
    EvonG1P
    Options

    Hey @WEMasters, thank you for your reply.

    It's no problem at all, we're happy to help. I'm glad to hear that updating the browser worked. 🙂

    Let us know if there's anything else we can help you with.

    -Evon

  • tianhuil
    tianhuil
    Community Member
    Options

    I have the exact same issue. Extension crashes as soon as I log in (but not before). It will flash the post-login screen (I can see my account info on 1password) but then crash. The error goes away as soon as dev tools is opened! But closing dev tools, the extension will immediately crash.

    [BackgroundStorage] Using browser.storage.persistent
background.js:2 [BackgroundStorage] Using browser.storage.session
background.js:2 👋 Initializing 1Password
background.js:2 channel: stable
version: 2.21.0
build: 22100001 (119.0.6045.199)
browser: Chrome (119.0.6045.199)
os: MacOSX (14.2.1)
background.js:2 WASM: Initializing.  Log Level: Info
background.js:2 💫 Looking for desktop app com.1password.1password
background.js:2 📤 Sending <NmRequestAccounts> message to native core <775250222>
background.js:2 👍 Finished initializing 1Password
background.js:2 📥 Received message <NmRequestAccounts> from native core <775250222>
background.js:2 📤 Sending <NmRequestAccounts> message to native core <3798884414>
background.js:2 📥 Received message <NmRequestAccounts> from native core <3798884414>
background.js:2 Hooray!; Unlocked account [censored] with MUK; 🎉
background.js:2 We successfully unlocked 1 account(s) from a Desktop app with 1 unlocked and 0 locked account(s).
background.js:2 📤 Sending <NmRequestDelegatedSession> message to native core <363065709>
background.js:2 📥 Received message <NmRequestDelegatedSession> from native core <363065709>
background.js:2 [LM] Started Desktop Lock Monitor at 1710606374441 (Connected to desktop app).
background.js:2 📤 Sending <NmLockState> message to native core <1676566780>
background.js:2 📥 Received message <NmLockState> from native core <1676566780>
background.js:2 📤 Sending <NmOfflineStatus> message to native core <583744680>
background.js:2 📥 Received message <NmOfflineStatus> from native core <583744680>
background.js:2 📤 Sending <NmOfflineStatus> message to native core <3698646492>
background.js:2 Loaded page details in 0.19999999552965164 ms.
background.js:2 Analyzed the page in 0.10000000149011612 ms.
background.js:2 📥 Received message <NmOfflineStatus> from native core <3698646492>
background.js:2 [popup] Not attempting to connect to desktop app: already connected or connecting to desktop app
background.js:2 Decided not to attempt reconnection to the desktop app.
background.js:2 📤 Sending <NmOfflineStatus> message to native core <3717814583>
background.js:2 📥 Received message <NmOfflineStatus> from native core <3717814583>
background.js:2 📤 Sending <NmLockState> message to native core <798949623>
background.js:2 📥 Received message <NmLockState> from native core <798949623>
  • tianhuil
    tianhuil
    Community Member
    Options

    I have the same issue.

    The extension crashes as soon as I log in (but it's OK when it won't crash if it has not been logged in. It briefly flashes the account info (I can see my logins / passwords) but then quickly shows the below error.

    The issue goes away when I open the dev tools for the background service worker. This is my current awkward workaround.

    The issue started a few days ago.

    Error log below, including configuration details (obviously, it did not crash because dev tools was open).

    [BackgroundStorage] Using browser.storage.persistent
background.js:2 [BackgroundStorage] Using browser.storage.session
background.js:2 👋 Initializing 1Password
background.js:2 channel: stable
version: 2.21.0
build: 22100001 (119.0.6045.199)
browser: Chrome (119.0.6045.199)
os: MacOSX (14.2.1)
background.js:2 WASM: Initializing.  Log Level: Info
background.js:2 💫 Looking for desktop app com.1password.1password
background.js:2 📤 Sending <NmRequestAccounts> message to native core <466795403>
background.js:2 👍 Finished initializing 1Password
background.js:2 📥 Received message <NmRequestAccounts> from native core <466795403>
background.js:2 📤 Sending <NmRequestAccounts> message to native core <888408700>
background.js:2 📥 Received message <NmRequestAccounts> from native core <888408700>
background.js:2 Hooray!; Unlocked account [censored] with MUK; 🎉
background.js:2 We successfully unlocked 1 account(s) from a Desktop app with 1 unlocked and 0 locked account(s).
background.js:2 📤 Sending <NmRequestDelegatedSession> message to native core <1379432506>
background.js:2 📥 Received message <NmRequestDelegatedSession> from native core <1379432506>
background.js:2 [LM] Started Desktop Lock Monitor at 1710605720626 (Connected to desktop app).
background.js:2 📤 Sending <NmLockState> message to native core <2005147296>
background.js:2 Failed to get active tab when checking for an open and fill tab
background.js:2 📥 Received message <NmLockState> from native core <2005147296>
background.js:2 📤 Sending <NmOfflineStatus> message to native core <3426873397>
background.js:2 📥 Received message <NmOfflineStatus> from native core <3426873397>
background.js:2 📤 Sending <NmOfflineStatus> message to native core <1164226558>
background.js:2 Loaded page details in 0.5 ms.
background.js:2 Analyzed the page in 0.10000000149011612 ms.
  • steph.giles
    steph.giles
    Options

    Hey @tianhuil,

    I'm sorry for the trouble, can you paste chrome://settings/help followed by the enter key into your address bar and check to see if you have any updates pending?

    I can see from the logs you have shared you are on Chrome 119.0.6045.199, the latest version is 122.0.6261.129.

    Let us know how that goes!

  • tianhuil
    tianhuil
    Community Member
    Options

    That worked! Thanks.

  • Dave_1P
    Dave_1P
    Options

    @tianhuil

    I'm happy that Steph's instructions helped to resolve the issue. 🙂

    -Dave