nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

nplastpass causing huge energy drain and processor use

f8ratiwtkod2

Lately when I'm using Firefox, it draws heavily on the CPU, running hot and revving up the fan. This even happens with only a single window open on a static webpage.

Using macOS Activity Monitor I've traced the problem to a process called nplastpass. When I disable the LastPass Firefox extension, the problem doesn't occur.

MacBook Air (2020)

Processor: 1.2 GHz Quad-Core Intel Core i7

Memory: 8 GB 3733 MHz LPDDR4X

macOS 12.3.1

Firefox 100.0

LastPass Firefox extension 4.94.0.3

Find more posts tagged with

Accepted answers

ray.d

I believe version 4.97.0 fixed the issue on my machine, Chrome V102.0.5005.115, macOS 12.3.1

All comments

Tommie Buford

I have the same issue, except that it doesn't apply only to FireFox. Any time I use LastPass to log into any website or app on my Mac, LastPass leaves an instance of nplastpass running. The issue is not tied to one browser in my case.

I can almost always tell it has happened because the fan on my MacBookPro will run up.

If I log into 3 different websites, there will be an instance of nplastpass for each log in. I've seen as many as ten instances of nplastpass running in Activity Monitor at one time. In fact, just logging into this forum caused an instance to start.

In FireFox or Chrome, the processor usage is usually between 50 and 60% for each instance. If I log in to any other app or service such as Zoom, there will be an instance for each of them that usually shows approximately 35% CPU usage for each instance.

If I delete the instances in Activity Monitor, fan speed will return to normal within a few seconds. Deleting them causes no problems that I have seen. Apparently, nplastpass is activated while logging in, then is no longer needed.

MacBook Pro (13-inch, Mid 2012)

Processor: 2.5 GHz Dual-Core Intel Core i5

Memory: 16 GB 1600 MHz DDR3

MacOS Catalina 10.15.7

formermember

Absolute nightmare.

Lastpass as of May 19 2022 has been slowing google services (chat, gmail) to a crawl. Causing CPU usage to 100%. Removing lastpass extension solves the problem.

Lastpass support is useless.

Chrome extension reviews are showing other users having this issue.

What the hell is going on . This is causing chaose for enterprise users such as myself.

Browser: Chrome (up to date)

Windows 11

ash.canon

Hi@Former Member I apologize for the recent difficulty there. We are actively investigating this behavioral change in LastPass and would like to gather logs from the affected machine. Are you able to speak with us over the phone when you have a few minutes to help troubleshoot? https://support.lastpass.com/help/how-do-i-contact-customer-support-for-lastpass-lp010121

f8ratiwtkod2

I guess @Former Member won't be helping you, but I'd gather logs if it would help you solve the problem. Would you like that @AshC?

Tommie Buford

I just updated the LastPass Firefox extension. There is no difference. It still leaves a nplastpass process running every time the extension is used to log into a website. That means if I log into 5 different sites, there will be 5 different nplastpass processes running, with each one hogging cpu.

I have double checked Chrome, Edge, and Safari. It seems LastPass is NOT leaving those processes running in those browsers now. It must be an issue with the Firefox extension.

ray.d

Hi, the issue really bothering us as Chrome is our main browser. I've done a little bit of research, the extension somehow is causing Gmail, especially Gmail with chat enabled cost a lot of CPU and memory resources. It gets better significantly if LastPass is disabled.

While waiting for your developer to fix this issue, I inspected the background.html, 1 of the js file is keeping log of something in the console, it generates a few logs per second, which could be a lead to debugging the problem. The screenshot of the console is attached

Could you please fix the issue ASAP? it is really slowing down our productivity. Thank you.

Tommie Buford

@CoryHI've also seen the same issue logging into the Zoom app. I'm not sure I understand that since I follow a link for the particular call that I take part in and don't actually log in via LastPass. The call appointment is saved to my Google calendar, so it may be that the log in happens behind the scenes via Chrome or the Calendar. I do not save passwords to the browser itself.

I'll have another Zoom call tomorrow and will see if the same issue happens again.

f8ratiwtkod2

That's interesting, @Bookman53.In light of the comments by the Chrome users on this thread, I'm wondering if we have two different problems here. Last week someone merged someone else's complaint with mine, but I'm not sure they're the same thing. Your issue sounds the same as mine, but with the update you now have a good experience with every browser except Firefox whereas these other users are still having problems with the Chrome extension.

ray.d

BTW, from Chrome version 101, the information in userAgent will be reduced till deprecate, use userAgentData instead.

ash.canon

@Bookman53 @CoryH @rayding We are actively investigating the cause of this behavior, but are having a hard time replicating it in our testing environments. If you're able to help us document further, please click my Community name to send a private message with your direct contact info, and the best time to gather some log files from your local device.

Thanks.

ray.d

update for the LastPass Chrome extension, I found it is acceptable if I open a Gmail tab with chat and then disable the LastPass extension, it will give me a few errors but seems to give up monitoring the tab, then it is safe to use the extension with other tabs although it still eats a lot of CPU but acceptable as long as you don't refresh the Gmail page. And the problem seems better on Chrome canary v104.

ryan.dickerson

We've had to disable the Chrome extension for our entire user base because it just drains CPU and Memory. Waiting for a fix from LastPass.

Tommie Buford

I've moved from Firefox to Safari simply it was getting tiresome having to go into Activity Monitor and delete the process(es) every time I logged in on a website.

ray.d

Is there a way to get rid of the onloadwff.js? It always troubled me even before the annoying issue. Or, it will be great if we can have an option to disable all the functions that let the Lastpass extension monitor the webpage, my browser is much smoother with the extension disabled. And my fan on the laptop is so quiet that I even can accept to switch LastPass off for most of the time, only enable it when I need to fill a login form.

frank.vanbraak

Having the same.. really slows down the entire PC/laptop... eventualy resulting in crashing the browser when f.e. 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..

ray.d

I suggest using one click extension manager to disable Lastpass extension when it is not needed, it helps me a lot to keep the laptop cool down from the high CPU usage, and the recently updated version does not solve the issue.

ash.canon

We believe enough information has been collected on this issue, and are working on the resolution currently.

Thanks for your patience.

steve

@AshC what's the update on this issue?

It's now been 20 days since it's been widely reported.

Are you going to credit accounts or offer compensation as the product has not be fully usable because of this?

glenn.dobson

Hi,

A fix for the high CPU usage will be included in the next release LastPass version 4.97.0 which we are in the process of releasing.

Tommie Buford

The problem does seem to have gone away in Chrome on Macs. I no longer see nplastpass processes running in Activity Monitor.

However, the problem is still very much alive in Firefox 101.0.1, which is the lastest version as of the time I'm writing this post.

I updated LastPass for MacOS to version 4.97.0. I then updated the Firefox extension to version 4.97.0.2.

It appears that nothing at all has changed with LastPass in Firefox. When I log into one website, LastPass still starts an nplastpass process. In Activity Monitor that process will run from about 55 - 62% cpu usage and will never quit unless forced.

If I then log into a second or third site, LastPass will drop a separate instance of nplastpass for each login. By now, there are two or three instances of nplastpass running - one for each log in. Those instances will run 40 - 50% cpu for each of them until they are forced to quit.

I can quit one or all of them. It makes no difference once I've logged into a website. Once the login is done, nplastpass appears to be a useless waste of cpu resources.

MacOS Catalina 10.15.7.

Firefox 101.0.1

Firefox extension 4.97.0.2

f8ratiwtkod2

That's rather surprising to me, @Bookman53 . I seem to have very similar specs as you, and the new version of the extensions seems to be working fine for me so far. The one difference between us is that I'm running macOS Monterey instead of Catalina.

MacBook Air (2020)

Processor: 1.2 GHz Quad-Core Intel Core i7

Memory: 8 GB 3733 MHz LPDDR4X

macOS 12.4

Firefox 101.0.1

LastPass Firefox extension 4.97.0

Tommie Buford

I have a mid-2012 MacBook Pro

2.5 Dual-Core Intel Core i5

16GB 1600 MHz DDR3

For some reason, Chrome is working fine, but Firefox is not right. Sometimes the first sign-in sets an nplastpass process with no CPU usage. Any logins after that will set more processes with high CPU. Other times, I can try it again, and every sign-in will set nplastpass with high CPU.