Intermittent Beachball Google Chrome 105 1Password 8.9.4 MacOS 12.5.1

OK, I've followed the steps you laid out and still tons of beach balling happening. I will email the logs and report. :)

Prior to following your steps I first disabled the 1Password extension from the Chrome extensions page, then re-enabled it... I then tried resizing my Chrome using Moom; it's instantaneous, no beach balling. I then tried autocompleting a password on a website using cmd-\, had tons of beach balling and Chrome freezing. The Chrome resizing is still instantaneous, though, for now.

I will now follow your exact steps and report back in a separate comment.

Hey @beaugunderson, does resetting the browser integration feature help with the issue? Here are the steps to do that (if you haven't done them yet):

1. Right-click the 1Password icon in your browser toolbar and choose Settings.
2. Under General, disable "Integrate with 1Password app".
3. Fully quit 1Password app and browser.
4. Restart the 1Password app and then open browser.
5. Right-click the 1Password icon in your browser toolbar and choose Settings.
6. Under General, re-enable "Integrate with 1Password app".
7. Test things out with the extension.

If that doesn't help, I'd like you to reproduce the issue and send over the following so we can take a closer look at what may be going on:

• The extension console log: https://support.1password.com/cs/extension-console-log/
• A diagnostics report: https://support.1password.com/diagnostics/

Attach the logs and diagnostics to an email message addressed to mailto:support+forum@1password.com.

With your email please include:

A link to this thread: https://1password.community/discussion/133605/intermittent-beachball-google-chrome-105-1password-8-9-4-macos-12-5-1
Your forum username: beaugunderson

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

Hey @ooglek, sorry about the issue you're seeing. It sounds like you went through the steps to reset the browser integration connection, which in some cases do help with the issue. However, if it does not, then we'd need to review things further.

I looked at your console logs but would also like to get a diagnostics report from you. Please reproduce the issue with filling and then send over updated logs as well as a diagnostics report from the 1Password 8 app:

• The extension console log: https://support.1password.com/cs/extension-console-log/
• A diagnostics report: https://support.1password.com/diagnostics/

Attach the logs and diagnostics to an email message addressed to mailto:support+forum@1password.com.

With your email please include:
* A link to this thread: https://1password.community/discussion/133605/intermittent-beachball-google-chrome-105-1password-8-9-4-macos-12-5-1
* Your forum username: ooglek

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

Another wrinkle: I use Moom to tile my windows to the left and right side of my screen. I use cmd+shift+left and cmd+shift+right to move to the left and right halves of my screen respectively. If I move the window of a Chrome profile with the 1password extension installed using this method I get a beach ball for 30 seconds before the window responds again.

If I move the window of a Chrome profile without the 1password extension installed it's instantaneous.

Also seeing this, the wait is interminable 😬

Spoke too soon, tried filling on another page in another Google Chrome window, got the beachball again. ARGH

I have followed @Joy_1P suggestion to remove the 1P app integration from the Google Chrome 1P Extension, shut Chrome/1P/1P Helper down, then start 1P then Chrome. That seems to have improved my immediate situation so far.

https://1password.community/discussion/132984/chrome-extension-not-working#latest

I will report back if I experience any additional failures.

Could someone at 1Password explain what this process does, why it helps, and why it cannot be automated for those less technically inclined?

ARGH -- just tried to post my comment and it failed.

Anyway, more detail here. Google Chrome goes unresponsive for 3 minutes trying to fill a login. I'll send the full console log to Support in case there is PII. I'll redact the relevant part here.

Also got a screenshot of the dead 1P dialog in the browser.

User Experience:
* 12:32:25 -- Hit command-backslash to fill a login
* Google Chrome beachballs, is unusable
* 12:33:05-ish -- Prompt states "Cannot determine if Chrome" prompt, hit "Fill Login"
* Google Chrome beachballs, is unusable
* 12:35:14 Google Chrome returns, nothing is filled in, I am le sad. [REDACTED]


12:32:25.375 background.js:2 📤 Sending <NmLockState> message to native core <[REDACTED]>
12:32:35.388 background.js:2 [LM] User went inactive. Posting lock notification.
12:32:35.389 background.js:2 [LM] Stopped.
12:32:35.389 background.js:2 [OP] Locked at Tue Sep 13 2022 12:32:35 GMT-0400 (Eastern Daylight Time)
12:33:05.398 background.js:2 signout failed: ClientError: The request took too long. Check your Internet connection and try again.
at new t (background.js:2:1124546)
at background.js:2:1642340
at Array.f (background.js:2:347162)
at background.js:2:346855
(anonymous) @ background.js:2
Promise.catch (async)
(anonymous) @ background.js:2
Promise.then (async)
(anonymous) @ background.js:2
FW @ background.js:2
signOut @ background.js:2
C8.lock @ background.js:2
mre @ background.js:2
Voe @ background.js:2
broadcastState @ background.js:2
updateState @ background.js:2
updateStateFromDesktopApp @ background.js:2
(anonymous) @ background.js:2
updateState @ background.js:2
nextState @ background.js:2
(anonymous) @ background.js:2
await in (anonymous) (async)
process @ background.js:2
(anonymous) @ background.js:2
setTimeout (async)
push @ background.js:2
invoke @ background.js:2
Fee.lockState @ background.js:2
Rne.didUserGoInactive @ background.js:2
Rne.queryState @ background.js:2
12:33:05.400 background.js:2 [OP] Locked at Tue Sep 13 2022 12:33:05 GMT-0400 (Eastern Daylight Time)
12:35:14.505 background.js:2 💫 Looking for desktop app com.1password.1password
12:35:14.505 background.js:2 📤 Sending <NmRequestAccounts> message to native core <[REDACTED]>
12:35:15.386 background.js:2 📥 Received message <NmRequestAccounts> from native core <[REDACTED]>
12:35:15.387 background.js:2 📤 Sending <NmRequestAccounts> message to native core <[REDACTED]>
12:35:16.014 extensions::setIcon:49 [Violation] 'load' handler took 268ms
12:35:16.036 background.js:2 📥 Received message <NmRequestAccounts> from native core <[REDACTED]>
12:35:16.472 background.js:2 Hooray!; Unlocked account [REDACTED] with MUK; 🎉
12:35:16.473 background.js:2 We successfully unlocked 1 account(s) from a Desktop app with 1 unlocked and 0 locked account(s).
12:35:17.243 background.js:2 [LM] Started Desktop Lock Monitor at [REDACTED] (connected to desktop app).
12:35:18.130 extensions::setIcon:49 [Violation] 'load' handler took 231ms


More details. Yes, I have a lot of browser tabs open in 3 windows. 1P7 + Extension didn't have an issue, so I believe that should be unrelated. Screenshot attached.

I will send the console log to 1P directly, because I'm not sure if there is PII in there or not.

12:32:25 -- I try to fill a login on a page
Google Chrome becomes unresponsive for 1 minute
12:33:05-ish -- Pops up "Could not verify" prompt, click "Fill Login"
Google Chrome becomes unresponsive for almost 2 more minutes
12:35:14 -- Finally can use Google Chrome Again.


12:32:25.375 background.js:2 📤 Sending <NmLockState> message to native core <[REDACTED]>
12:32:35.388 background.js:2 [LM] User went inactive. Posting lock notification.
12:32:35.389 background.js:2 [LM] Stopped.
12:32:35.389 background.js:2 [OP] Locked at Tue Sep 13 2022 12:32:35 GMT-0400 (Eastern Daylight Time)
12:33:05.398 background.js:2 signout failed: ClientError: The request took too long. Check your Internet connection and try again.
at new t (background.js:2:1124546)
at background.js:2:1642340
at Array.f (background.js:2:347162)
at background.js:2:346855
12:33:05.400 background.js:2 [OP] Locked at Tue Sep 13 2022 12:33:05 GMT-0400 (Eastern Daylight Time)
12:35:14.505 background.js:2 💫 Looking for desktop app com.1password.1password
12:35:14.505 background.js:2 📤 Sending <NmRequestAccounts> message to native core <[REDACTED]>
12:35:15.386 background.js:2 📥 Received message <NmRequestAccounts> from native core <[REDACTED]>
12:35:15.387 background.js:2 📤 Sending <NmRequestAccounts> message to native core <[REDACTED]>
12:35:16.014 extensions::setIcon:49 [Violation] 'load' handler took 268ms
12:35:16.036 background.js:2 📥 Received message <NmRequestAccounts> from native core <[REDACTED]>
12:35:16.472 background.js:2 Hooray!; Unlocked account [REDACTED] with MUK; 🎉
12:35:16.473 background.js:2 We successfully unlocked 1 account(s) from a Desktop app with 1 unlocked and 0 locked account(s).
12:35:17.243 background.js:2 [LM] Started Desktop Lock Monitor at 1663086917243 (connected to desktop app).
12:35:18.130 extensions::setIcon:49 [Violation] 'load' handler took 231ms