1PasswordSLSNativeMessageHost Google Chrome Beta 100 Saturating CPU

I just signed up for 1Password yesterday. I've got both the app and Chrome extension downloaded and working on my MacBook Air. I've been in Chrome the past couple days going through 50+ sites updating passwords so far.

My computer had slowed to a crawl and the fan was going full blast. I went into activity monitor and there were several dozen '1PasswordSLSNativeMessageHost' processes going. I did a quick Google search about native messaging, but it's not something I'm familiar with.

I quit all the processes and my computer is back to normal. How is this something I can prevent going forward? Thanks

1Password Version: Not Provided
Extension Version: 2.3.2
_OS Version: Not Provided

Thanks for the response. I don't see a version 2.3.3 in the Chrome store, and I'm still on version 2.3.2. Does it auto-update somehow?

Just want to add that this is still happening as of March 25th.

The biggest problem for me: this affects all of my company employees's because we use 1Password Enterprise. Support tickets just went through the roof!

Hey @cvince86/ @wbobeirne / @salty / tmarquard:

Thanks for following up on this. We've recently made some improvements in version 2.3.3 of 1Password in the browser that should hopefully improve the state of play here. After ensuring that 1Password in the browser is up to date, fully quit both Chrome and 1Password for Mac (Hold down the Control and Option keys on your keyboard and choose 1Password > Quit 1Password Completely from the menu bar). Reopen Chrome and 1Password for Mac, and let me know how that goes.

Jack

This affects PRODUCTION chrome Version 99.0.4844.83 (Official Build) (arm64) as well.

For now I'm removing 1password extension from Chrome. If this doesn't get fixed soon I'm probably gonna switch to dashlane. This kind of bug is completely unacceptable for such sensitive software.

It almost makes me feel like I'm being hacked or something.

Hi @wbobeirne / @salty / tmarquard:

Thanks for adding your input! As I mentioned above, we're actively investigating, and hope to know more, but in the meantime the steps I provided above should improve the state of play.

Jack

Also just experienced this, hundreds of processes and was completely locking up my system. Also got a few prompts initially about it not being able to validate Chrome or something like that.

macOS 12.2.1 (21D62)
Apple M1 Pro 32gb
Version 99.0.4844.74 (Official Build) (arm64)
1Password Extension 2.3.0
1Password Desktop 7.9.3 (App Store)

I disabled the Preferences > Browsers > Always keep 1Password Extension Helper Running setting and manually killed all the processes and the issue is gone for now. Would love to see a fix come in soon though.

Same here, Chrome Version 99.0.4844.74 (Official Build) (x86_64), MacOS 12.2.1 (21D62)

My load average was over 1000! and hundreds of these processes running and more spawning all the time. I started trying to kill them but they kept spawning, eventually I went into the browser and disabled the extension, and when I was trying to kill the remaining processes my machine spontaneously rebooted.

todd 7230 3.5 0.1 33797240 13472 ?? R 2:00PM 0:01.11 /Applications/1Password 7.app/Contents/Library/LoginItems/1Password Extension Helper.app/Contents/MacOS/1PasswordSLSNativeMessageHost chrome-extension://aeblfdkhhhdcdjpifhhbdiojplfjncoa/
todd 1988 3.5 0.1 33796204 11028 ?? R 1:27PM 1:12.20 /Applications/1Password 7.app/Contents/Library/LoginItems/1Password Extension Helper.app/Contents/MacOS/1PasswordSLSNativeMessageHost chrome-extension://aeblfdkhhhdcdjpifhhbdiojplfjncoa/
todd 6070 3.5 0.1 33796716 10212 ?? R 1:43PM 0:22.98 /Applications/1Password 7.app/Contents/Library/LoginItems/1Password Extension Helper.app/Contents/MacOS/1PasswordSLSNativeMessageHost chrome-extension://aeblfdkhhhdcdjpifhhbdiojplfjncoa/

I am also seeing the same issue. MacOS 12.2.1; Chrome Version 99.0.4844.83 (Official Build) (x86_64); 1Password Version 7.9.3 (70903003). Have disabled the chrome extension. Looking forward to hearing a solution.
Thanks

Hi @KatFlip / @wookieunderwood @joelmlevin:

Thanks for following up. We're actively investigating the cause of this, but in the meantime, disabling "Integrate with 1Password desktop app" in 1Password in the browser's settings should improve your state of play. To do this, right click the 1Password icon in Chrome's toolbar, choose Settings, then disable "Integrate with 1Password desktop app". With the integration disabled, you will have to unlock 1Password in Chrome separately from the 1Password desktop app, but it should resolve the processes being spawned. Keep an eye out for updates as we work to resolve this issue.

Jack