Mac - Chrome Extension Keeps Crashing

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.

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

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

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>


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.


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!

That worked! Thanks.

@tianhuil

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

-Dave