Thanks @john.eastberg
The temporary fix may not show the performance improvement right away, but take several minutes for the background actions to level out.Please let us know if the high CPU behavior persists after 10+ minutes using LastPass version 4.139.3.
I'm having the same issues. Latest Chrome and Edge on Windows 11 and MacOS 15. I've disabled the extension in both until there is a resolution.
Hi, folks.
I'm sorry about the recent change in resource demands by LastPass.
Rest assured this is a very high priority fix for our team, and we expect to start rolling out an update next week to address the issue.
Thanks for your patience while we finalize testing.
Can confirm, this is happening whole time extension is not disabled (one option to resolve it is to limit access to websites by click).
Looking forward for update, thanks.
This is unfortunate. I have been a LastPass Premium subscriber for many years, but this issue and the inability to provide a timely resolution has caused me to cancel my upcoming renewal (in March) and whereas I require a solution that works and does not hinder my daily activities I have since migrated my password(s) for 1,000 accounts to a competing solution. Best of luck going forward.
what patch?
It's 'next week' now, can you share a progress update for fixing this? It's extremely annoying, and I can't really use the browser with the extension enabled. Which makes it useless in this state.
Hi, just joined the thread, I too am having this issue. The first thing I did was uninstall and reinstall extension. I've confirmed version 4.139.3. Below is the Chrome task manager output.
Thanks for your patience, everyone.
Please perform a full re-install of the LastPass app to receive version 4.139.3, then log back into your account and please let us know if the issue remains.
I can confirm that version 4.139.3 does not solve the issue. The extension still has extremely high CPU usage and continues to be unusable.
What is the target date for the next release and is it 100% sure that it will fix the problem?
And here is another idea: why don't you just roll back the changes you made that caused the issue? Fix it for everybody, then take you time, and actually test the next release?
