Bitwarde Helper for Mac uses more CPU time than anything else
Steps To Reproduce
Expected Result
Seems like a bug.
Mac running latest MacOS 26.0.1 Bitwarde version: Version 2025.10.0 SDK 'main (d0262d3)' Shell 36.9.3 Renderer 136.0.7103.177 Node 22.19.0 Architecture arm64
Actual Result
CPU time is enormous
Screenshots or Videos
No response
Additional Context
No response
Operating System
macOS
Operating System Version
26.0.1
Installation method
Apple Appstore for Mac
Build Version
2025.10.0
Issue Tracking Info
- [x] I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Thank you for reporting this issue! We've added this to our internal tracking system. ID: PM-27683 Link (for internal use): https://bitwarden.atlassian.net/browse/PM-27683
Hi there,
This issue has been escalated for further investigation. If you have more information that can help us, please add it below.
Thanks!
Possibly related to https://github.com/bitwarden/clients/issues/17128
I can confirm this issue.
MacOS Tahoe 26.1 Bitwarden Version 2025.10.0 Architecture arm64
Can confirm, having same issue, - MacOS Tahoe 26.1 (arm64), Bitwarden 2025.10.0.
Confirmed.
Bitwarden 2025.11.1 (51183) Tahoe 26.1 (25B78) (arm64)
yeah what the heck is it doing? quitting and restarting bitwarden on desktop fixes the issue. but you have to do this periodically.
Confirmed here.
Bitwarden 2025.11.2 (51375)
macOS 26.1
M1 Pro 14" MBP
I happen to have reinstalled macOS recently, and experienced this before and after reinstallation, even on the fresh install.
Just wanted to update on the workaround I'm now using daily, which others may find useful. To make my browser usable (e.g. to be able to type in text boxes), I have to keep Bitwarden disabled by default. When I need to sign in to a site, I:
- Open the extensions pane,
- Toggle Bitwarden to enabled,
- Log in, and then
- Toggle the extension to disabled again.
Looking forward to the day this isn't necessary :)
Just chiming in to confirm this issue on my end.
M5 MBP MacOS 26.2RC 25C56 48 hours of system uptime, 3:18:33 cpu time on the Helper.
Like others have said, restarting the desktop app appears to temporarily fix the issue.