MacOS 10.14.6
If the computer is going into hibernation before an inactivity timeout, then the clock stops and won't terminate the session. People should have an operating system password anyways, and lock the machine when they're not present.
Fair comment about hibernation, but LastPass still does not auto logout as advertised when the computer is fully awake but fully inactive.
Reasonable to have to lock your computer, but my operating system password is not as strong as my LastPass since LastPass secures all my assets.
The auto logout has worked at times in the past. Not now. The web page auto logout works. Maybe a tab on my Chrome has something that looks to LastPass like keyboard or mouse activity (which it is not).
So finally, I maintain that is a Major Security Bug in the extension. Since I am a free user, I cant get support.
Same issue on Windows 11 with current versions of LastPass extension, Chrome, and Windows
Same here on win11 23H2 , never had any issues but since a week or so it doesnt log me out anymore. Change the timeout to trigger it but stays logged in.
It's now ... mostly. The frontend software seems not crisp and this is a larger concern. Here are the steps for Windows. After doing this for 3 computers I am not certain whether any of it is optional.
Good luck
I am having the same issue on Win 10 and Win 11, up-to-date Chrome. I have uninstalled and refreshed and cleared local data and reinstalled just the browser extension. I am tracking this issue with LastpassSupport Case 02597476 and am getting nowhere.
I have a MacBook and MacMini. Lastpass chrome extension never auto logs out of either. Definitely a concern.
I upgraded MacBook, Chrome and LP extension to latest. Now it is safe! But this is because it auto logs out from the vault ,and the extension, after a few minutes of non use. And I have to log back in twice, the first time it seems to internally complete the auto log out!
I agree with @User17153903806965212011 above. Bitwarden is a very good alternative.
This problem was resolved briefly but returned around 4.131. I am deeply concerned about the ability of LastPass to deliver stable software. Pretty alarming for 1) a mature product and 2) a product delivering safe security software. Any recommendations for more stable alternatives?
I have had the same issue were the inactivity time does not work.. this has affected all 4 of my devices...all are Windows 10 or Windows 11 and all have the Chrome extension. It always used to work until around 2 month ago it quit. I opened a ticket months ago and as far as the tech is concerned my problem is unique...clearly not based on the comments here. I too saw that a coule of weeks ago when Lastpass updated the extension that it worked for a few days and then started failing again and now never works. Lastpass doensn't seem to be in any hurry to fix it.
You are not alone. LP did seem to properly timeout for a couple days on my Windows 10 Chrome, but it's back to being broken on Windows 10 and 11.
Not getting anywhere with Lastpass... have signed up for BitWarden and started the transition. A bit of a learning curve but seems to be doing what it should. As for Lastpass... good luck to them,
My upgraded MacOS, Chrome, and LP extension has reverted to bad old behaviour. UNSAFE. Never auto logs out.
The problem persists for me even with Chrome extension V. 4.131.4 (Windows 11 computer). It stays logged in even overnight. (I have the timeout set to 10 minutes.)
For what it is worth Lastpass released a new Chrome extension V. 4.131.4 a day or two ago. So far it appears to have addressed the problem as it now logs us out after the inactivity timer expires. The dirrefence seems to be that it is Lastpass specific activity that it is timing and not you using your device. I you are using Word or Excel and not your browse it will log you out when the time comes. I suppose that is not a bad thing in itself. As I have seen in the past where a new extension seemed to have fixed the problem only to revert to not working again a day or two later we would have to wait to see before saying it is fixed.
Same problem here. I initially thought it was my problem alone. But doesn't seem like it. Unbelievable that it is not getting any attention even after so many people having brought this to lastpass attention.
I just submitted another support ticket b/c we have this same issue as well. I'm hoping it'll get escalated through to the tech team as it seems obvious this isn't an isolated issue. (I also linked to this thread in that ticket so the initial team member sees that this isn't one of those "update your software" type of solutions. It seems as if something is off in the codebase that causes the extension to ignore timeout rules and doesn't seem to be contained to Mac or Windows (in our case, it's Windows).
Hopefully it helps and as I get any resolution I'll post an update here for everyone.
Amazing! The timeout has been working for me now for a couple of weeks. I dont know what did it - presumably a bug fix -I have not tried changing any settings.
I've been experiencing the same issue with the LastPass Chrome extension. It seems that if I set the inactivity timeout to a very low value (1-5 minutes), the timeout feature works as expected. However, when I increase the timeout to 20 minutes or more, it fails to log out as it should.
Additionally, I've noticed that when the timeout fails and LastPass remains logged in, the browser shortcut (lp <Tab>) also stops functioning correctly. While it still triggers LastPass, it doesn't return any results from my Vault. The extension's window still allows me to search and access my Vault without any issues.
Has anyone found a solution or workaround for this? Any insights would be appreciated!
I've seen Reddit threads that talk about how to install older versions, but I'm not sure which older version is stable at this point. I suspect this bug is the result of an attempt to fix a different bug that was causing the extension to log out too quickly, but I don't know for sure. Completely exiting Firefox seems to be one workaround.
Things have been working for me this week all of a sudden... using Windows 11 Chrome Extension Version: 4.133.0.
Seems to be paying attention to timeouts as well as the policy of only allowing one device to be logged in at a time (just like the old day!). Fingers crossed this one has solved something and will report back if it changes.
This has been an issue for me since I started using LastPass many years ago, and it is still an issue in 2025.
On my laptop, in LastPass for Chrome, the "Log out after this many minutes of inactivity" setting is set to 120 minutes. Yet, it hasn't locked for weeks.
A gaping security hole. I'm moving to a competitor.
Hi, @lolmaus​
Have you also checked your trusted device settings to confirm there isn't a preferential setting engaged?
