Hi there, many folks in my company, myself included, are experiencing huge performance issues in the last 2-3 days with the lastpass chrome extension. It basically completely consumes any available CPU resources.
I am having trouble having more than 4-5 chrome tabs open when lastpass enabled all of a sudden. I used to be able to have 20 tabs open with no problem.
To recreate... we open chrome from scratch (no browser tabs previously open) when the lastpass extension is enabled by default.
Open 4-5 chrome tabs.
CPU climbs to 100% and stays there, never declines.
Go into Chrome settings, disable the extension, cpu resources drop to around 10% used.
It is reliably reproduceable by many of us.
laptop = Windows 10 64 bit, 24GB memory
Version = 4.95.0
Seems to have just started in the last 2-3 days.
Solved! Go to Solution.
@cling33 We're working to identify the cause of this behavior currently. I expect a resolution very soon.
Thanks for you patience.
Having the same.. eventualy resulting in crashing the browser when using Google Ads Editor with message: sbox_fatal_memory_exceeded and using 10Gb of memory... Also other sites are slow and the cooling fans from the laptops are going crazy... Please fix asap..
We're having this issue in our organization. Had to disable LastPass for the entire organization since every user's machine is maxing at 100% CPU and going crazy. We have a ticket into LP support but they have no idea what the issue is or how to fix it. Won't even look into a work around. Have escalated twice, been getting canned responses.
We're talking to the sales team at Bitwarden at the moment since we can't go without a password manager for weeks on end while they "look into" this issue. If there is this large of an issue, they should have rolled back the update or done something instead of just saying they're "looking into it". Disappointed but not surprised. We left LogMeIn Central last year for SolarWinds Dameware for the same reason. Support is basically non-existant for any LMI products.
Guess we'll just limp along for now and look at alternatives since this simply doesn't seem to be a priority for the LMI team to try and fix.
We are working to resolve this issue now, and I expect more info from the team in the coming days. Thanks for your patience.
@AshC You've been saying this for almost 2 weeks now.
Do you have anything productive to add to this huge issue?
We have already reported the extension to Google as harmful because it simply is. It's causing overheating issues which can potentially damage the PCs
So, is there any workaround we can use in the meantime? Right now, we've basically told our entire organization that they need to sign out of LastPass and only sign in when they need a password, then once they're logged into the site that they need, log back out before their CPU usage spikes and ramps up their fans.
This is obviously less than ideal and there is a lot of lost productivity with people just signing in and out of LastPass all day. Can LastPass roll back whatever update caused this while they work on fixing it?
We are given no ETA on a fix and just told "they're working on it". Sorry, that's not really good enough. I understand that development takes time and there's no magic fix, but just a little transparency can go a long way. Even if you don't have an exact ETA, some kind of timeframe would be nice. Will it be days? Weeks? Months?
A lot of us at my org have changed the chrome permissions for lastpass so that a user needs to click on it to allow it to have access to the page. Not sure if that is better or worse than signing in and out.