Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
1PasswordSLS running multiple instances after extension added to Chrome
I recently added the 1Password extension to Chrome. Soon thereafter my system is sluggish. When looking at top I see a large number of 1PasswordSLS processes ... when I kill Chrome they go away. I then needed to uninstall the extension.
Is there a fix for this ?
Processes: 625 total, 162 running, 463 sleeping, 3627 threads 11:12:26
Load Avg: 271.53, 223.06, 132.51 CPU usage: 40.93% user, 59.6% sys, 0.0% idle SharedLibs: 785M resident, 112M data, 88M linkedit.
MemRegions: 159587 total, 7261M resident, 777M private, 5053M shared. PhysMem: 31G used (2161M wired), 31G unused.
VM: 234T vsize, 3780M framework vsize, 0(0) swapins, 0(0) swapouts. Networks: packets: 2064454/827M in, 1767152/1007M out.
Disks: 9918453/99G read, 754686/19G written.
PID COMMAND %CPU TIME #TH #WQ #PORT MEM PURG CMPR PGRP PPID STATE BOOSTS %CPU_ME %CPU_OTHRS UID FAULTS
9078 1PasswordSLS 25.2 04:10.63 3/1 2/1 54 6721K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1533
9071 1PasswordSLS 24.8 04:12.73 3/1 2/1 54 6705K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1532
9286 1PasswordSLS 24.8 00:13.01 3/1 2/1 53 6465K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1506
9284 1PasswordSLS 24.7 00:14.26 3/1 2/1 54 6561K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1510
9114 1PasswordSLS 24.3 03:10.42 3/1 2/1 53 6673K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1527
7896 Meeting Cent 24.3 14:01.06 70/1 9 1187 524M 44M+ 0B 7896 1 running *1[14] 0.36005 0.00000 501 347259+
9246 1PasswordSLS 24.3 00:49.73 3/1 2/1 54 6753K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1520
9072 1PasswordSLS 24.1 04:12.52 3/1 2/1 54 6705K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1532
9292 1PasswordSLS 23.9 00:07.55 3/1 2/1 53 6497K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1509
9245 1PasswordSLS 23.8 00:50.12 3/1 2/1 53 6577K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1511
9076 1PasswordSLS 23.8 04:11.87 3/1 2/1 54 6673K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1531
9085 1PasswordSLS 23.7 04:11.85 3/1 2/1 54 6753K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1534
9069 1PasswordSLS 23.7 04:13.07 3/1 2/1 54 6737K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1533
9241 1PasswordSLS 23.6 00:53.20 3/1 2/1 54 6657K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1516
9199 1PasswordSLS 23.6 01:34.65 3/1 2/1 52 6705K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1524
9073 1PasswordSLS 23.3 04:11.22 3/1 2/1 53 6737K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1532
9274 1PasswordSLS 23.3 00:26.40 3/1 2/1 53 6641K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1514
9227 1PasswordSLS 23.3 01:13.87 3/1 2/1 54 6625K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1519
9266 1PasswordSLS 23.3 00:30.44 3/1 2/1 53 6529K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1510
9213 1PasswordSLS 23.2 01:17.37 3/1 2/1 54 6657K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1521
9276 1PasswordSLS 23.2 00:23.82 3/1 2/1 54 6577K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1511
9112 1PasswordSLS 23.2 03:11.17 3/1 2/1 54 6737K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1532
9116 1PasswordSLS 23.2 03:09.63 3/1 2/1 53 6673K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1528
9202 1PasswordSLS 23.0 01:30.12 3/1 2/1 54 6609K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1518
9115 1PasswordSLS 23.0 03:09.01 3/1 2/1 54 6609K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1522
9271 1PasswordSLS 22.9 00:28.65 3/1 2/1 54 6545K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1508
9253 1PasswordSLS 22.9 00:38.20 3/1 2/1 53 6497K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1506
9198 1PasswordSLS 22.6 01:35.29 3/1 2/1 54 6673K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1522
9081 1PasswordSLS 22.4 04:10.82 3/1 2/1 54 6865K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1540
9239 1PasswordSLS 22.2 00:53.79 3/1 2/1 53 6577K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1513
9118 1PasswordSLS 22.1 03:07.41 3/1 2/1 52 6657K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1528
9243 1PasswordSLS 22.1 00:50.57 3/1 2/1 53 6673K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1518
9086 1PasswordSLS 22.1 04:10.19 3/1 2/1 53 6641K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1526
9237 1PasswordSLS 22.0 00:56.87 3/1 2/1 54 6721K 0B 0B 661 661 running *0[1] 0.00000 0.00000 501 1519
9183 1PasswordSLS 22.0 02:25.67 3/1 2/1 53 6706K 0B 0B 661 661 running *0[2] 0.00000 0.00000 501 1529
1Password Version: 7.9.1
Extension Version: 2.3.0
OS Version: Monterey 12.2.1
Referrer: forum-search:https://1password.community/search?Search=1passwordsls
11 Replies
1P_Ben1Password Team
Hi all,
We believe we've got this fixed up in 1Password for Mac 7.9.4. Please give that a try as soon as the update becomes available for you and let us know how it goes. It is available today for folks who update directly through the app, and will be available through the App Store as soon as it makes it through the submission & approval process.
Ben
- 1P_Dave
Moderator
@dmj111
Thank you for posting the Support ID number. I see that you're already in conversation with one of my colleagues and I recommend continuing the investigation over email. To prevent duplication of effort, I'm closing this thread. 🙂
ref: ZLT-77799-976
- 1P_Dave
@dmj111
I'm sorry to hear that you're running into the "1PasswordSLSNativeMessageHost" issue, we're still investigating and hopefully we'll have a fix out soon. In the meantime turning off app integration as Jack described here would be the best workaround.
FWIW: with the integration enabled I already have to unlock 1password in chrome even if the desktop app is open.
That doesn't sound right. 🤔 To investigate this further, I'd like to ask you to create a diagnostics report from your Mac:
Sending Diagnostics Reports (Mac)
Attach the diagnostics to an email message addressed to
support+forum@1password.com.With your email please include:
- A link to this thread: https://1password.community/discussion/127899/1passwordsls-running-multiple-instances-after-extension-added-to-chrome
- Your forum username:
dmj111 - Please do not post your diagnostic report to the forum. This is for your privacy and security. The report will be in zip format. Please send the entire file.
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
Seeing similar issues. I upgraded to 7.9.3 yesterday, and was just struck again with the spawned process issue.
OSX: 11.6.4
Chrome: Version 99.0.4844.83
1Password: 7.9.3
1Password chrome extension: Version
2.3.0FWIW: with the integration enabled I already have to unlock 1password in chrome even if the desktop app is open.
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.
Jack_P_1PHi @DominikD / @jnsp:
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
I have the same problem though I had it updated 7.9.3.
$ ps aux | grep 1Pass
user 45564 14.7 0.1 408468224 20480 ?? R 9:43PM 1:19.63 /Applications/1Password 7.app/Contents/Library/LoginItems/1Password Extension Helper.app/Contents/MacOS/1PasswordSLSNativeMessageHost chrome-extension://aeblfdkhhhdcdjpifhhbdiojplfjncoa/
...$ ps aux | grep 1Pass | wc -l
155It has 155 processes! CPU overloaded 100%. The only solution for me is 'Force Quit' Chrome everytime.
- Jack_P_1P
You're very welcome @nepife!
