Chrome plug-in hangs

Hi @Kevin10, thanks for the info. We're not saying that the issue is isolated. However, there are a lot of different reasons why the extension may be acting up. We do have to look at your setup individually in order to determine what is going on.

Does this behavior occur if you do not have as many tabs open?
I always have that many tabs open. I've had that many tabs going on 2-3 years straight. I'm not going to bookmark them all just so I can close them all to test this, sorry. I had the browser extension working with those tabs open for quite some time until recently.

If you are unable to test that, can you tell us if you notice any issues with your computer's memory with all those tabs open? Do you use 1Password in any other browsers and if so, does the issue occur there when there are only a small number of tabs open?

Again, our goal isn't to have you close the tabs -- we want to see if that is where the issue is coming from.

Do you have any other extensions installed in Chrome? If so, what are they?
Yes, "Malwarebytes Browser Guard" and "GoFullPage - Full Page Screen Capture" but I tried disabling both of them and the issue still persists.

Do you have any anti-virus or anti-malware programs on your computer?
Yes, Malwarebytes endpoint protection under a Malwarebytes business subscription.

Can you temporarily turn off those other extensions, turn off your Malwarebytes antivirus, reproduce the issue with 1Password in your browser, and then send us the following for further investigation?

• 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/comment/682844#Comment_682844
* Your forum username: Kevin10

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

I'm again having the exact same experience as @Kevin10 . The beta plugin worked for like a day or two and then this same issue came back.

One thing I noticed is that when the Brave extension becomes unresponsive, it becomes unresponsive in Firefox as well. During this time, the 1Password app works as expected.

I'm seeing this issue on two different computers: Mac Intel and Mac Apple Silicon. My coworkers have a very similar setup but haven't experienced these issues.

Hi @Joy_1P

1. No issues with system memory, no.
   

2. I added the 1password add-on to Firefox and that has been working fine even while the Chrome add-on is hung up and doing nothing.

3. I Uninstalled Malwarebytes, Disabled all other Chrome extensions, Updated to the latest version of MacOS Monterey, updated to the latest version of Chrome, and did a fresh reboot. The problem with the Chrome add-on still persists.

4. I've generated the requested logs along with some screenshots with timestamps to correlate to those logs. I will note that I was seeing some 1password console logs in my regular inspector window, even before enabling developer mode in the Manage Extensions pane. I included those as well, the filenames tell the difference. I also saved off a copy of the network logs from the extension inspector window as a HAR file, but I did not send that along in my email to support because I didn't know if those network headers and cookies could contain secret information that should not be shared. I did notice some 404 errors in the network pane during my testing, FYI.

5. I noticed frequent statements in the console logs that the service worker was being reloaded due to a setting (Application > Service Workers > Update on reload). It appears that setting is not on by default so I've disabled it and will report back after a few days if that has made a significant improvement.

Support Ticket Number: 127550

End of day status update : Having that Service Workers setting unchecked has produced good results so-far. Fingers crossed!

Thank you for the update @Kevin10, let us know if there's anything else we can help with at all.