Performance issue when 1Password locks
I've noticed that CPU spikes to about 5-10% and GPU to about 5% on my machine whenever 1Password locks. This causes the fan on my laptop to activate. What is 1Password doing when it is locked, and can it be disabled?
Windows Version 1803, build 17134.112. Processor is Intel Core i5-8250U @ 1.60 GHz.
I've tried keeping the console open to see if I could figure out anything, but nothing I could see.
1Password Version: 7.1.567
Extension Version: Not Provided
OS Version: Win 1803, 17124.112
Sync Type: Not Provided
Comments
-
Hi there @cczz,
Thank you for reporting this!
First of all, could you please specify, are you using a local vault in 1Password 7 or 1Password account? If it is the former, I have a hunch of what might be going on. In order to confirm it, I'd like to ask you to create a Diagnostics Report from your laptop, where you see this behaviour:
Sending Diagnostics Reports
Attach the Diagnostics Report to an email message addressed to support+windows@agilebits.com.
Please do not post your Diagnostic Report in the forums, but please do include a link to this thread in your email, along with your forum handle so that we can "connect the dots" when we see your report in our inbox.
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here so we can track down the report and ensure that this issue is dealt with quickly. :)
Cheers,
Greg0 -
could you please specify, are you using a local vault in 1Password 7 or 1Password account?
I'm using my 1Password Account. Sent in the report, thanks.
0 -
Thanks! I see that we've received your email, so we can continue the conversation there. We'll take a look at the diagnostics and get back to you as soon as we can! :)
ref: BDA-28579-497
0 -
1Password process uses a high amount of CPU and GPU resources for me as well, when 1Password application is locked. Version is 7.2.576. I noticed this behavior in earlier versions too. I'm using local vaults. This is a new installation in a new computer with i7-8550U with dGPU disabled altogether in Windows environment. Heavy resource usage happens only when the application is running, vault is locked and the application window is not minimized. I'm not using any browser integration either. The image shows the usual resource usage in the aforementioned situation.
I'm sorry, but for my paranoid reasons, I won't be able to send you the full diagnostic report without heavy sanitizing (I'm inclined to not trust anyone with that kind of information that your diagnostic tool provides) but I'm more than happy to submit parts of my diagnostic report with some sanitizing. I already started to analyze the memory dumps of your process but I wanted to let you guys know that user cczz is not the only one with these performance issues. As you can understand, it's slightly irritating that forgetting to minimize 1Password window is causing such a high resource usage.
0 -
@veriik: Thans for getting in touch. We're working on a number of optimizations for an update, and I think it will help in your case too. But just to confirm, if you close the main 1Password window, does that decrease the resource usage?
And just to clarify, a diagnostics report doesn't include personal information (unless you've used sensitive details as part of your Windows user account name, etc.)
0 -
@brenty: I consider a lot of information about my setup as personal information that shouldn't be available to anyone except me. List of running programs, username etc. The less there is data with correlation, the better.
The resource usage is the worst by far in the case I described. It's actually tolerable when the vault is unlocked and the window is open and not minimized. The CPU and GPU usage go down to almost zero as well, when the application window is minimized and vault is locked.
0 -
@verlik: You're always welcome to sanitize your diagnostics as much as you see fit. I will tell you that removing things like running processes can sometimes hamper troubleshooting of certain issues. I say this not to try to encourage you to send data you don't want to (that's totally your call), but just to let you know that there's a non-zero chance you'll be in for some additional back-and-forth if anything gives indication of third-party interference or other issues that might require some additional info to diagnose. We don't mind that at all and are happy to work through things with questions as needed if it makes you more comfortable, this is just meant as an FYI.
And, again, as Brenty said, we're in the process of some optimizations that certainly have a chance of helping here. 1Password has learned a few too many new tricks lately and we've seen enough performance issues that manifest in various ways for different folks that we've been working on a sizable project to increase efficiency and improve performance across the board. It's not something that will happen overnight, of course, and we'll likely have some additional tweaks to make once these changes get out in the wild and we see what does and doesn't resolve, but it's definitely at the forefront of our minds right now.
All the same, you're welcome to send diagnostics (sanitized to your liking) and we'd be happy to take a look. Out of curiosity, I took a peek at my resource usage with 1Password locked and it hardly touches my GPU (spikes to 5% at most, but is at or near 0% most of the time) and CPU hovers around 2%, so might be there's some tweaks that can be made now to improve things. My PC does double duty for work and gaming so it may not be the best indicator of 1Password's performance on most systems, but you do have me beat in the CPU category, so you never know. :wink:
0 -
@verlik sorry for the trouble, it's lock animation that runs when app window is visible and app is locked. It's supposed to be "self-adjusted" by your system, but apparently it's taking too much of resources for too little value. Upcoming update will have that animation off when window is not focused. For now just close that window (or minimize it), so it will not waste your battery.
Also, :highfive: on being a little paranoid about Diagnostics Report. It's actually safe and we (including me personally) regularly check that there is no private/sensitive/personal information leaked there. But I'm always happy when our words being put to test, can't be too careful here.
0 -
I know this is a bit late to the conversation, but I found the help in the form of 7.2.580 beta. None of the issues I mentioned in my original message persist anymore. Locking animation seems to running constantly though when the application window is in the foreground (it is the only case with high resource usage). Is this intentional? Wouldn't it be more beneficial to initiate animations only when there is some action in the application window? Needless to say, I enjoy only programming in very low level languages, I'm not a Windows dev.
About diagnostic reports: It's hard or impossible to know how the report is stored and analyzed. I'm paranoid of the correlation capabilities that some systems (general type of AI with superior amounts of data) might poses in the near future and in general I try to limit data output from my systems. Installed or running programs fall into this category for me. I very much understand, that from debugging perspective it's absolutely vital information in some cases to be able to see, what programs were running simultaneously. Sadly, there is quite often the conflict between secrecy and accessibility of information for good purposes. Sometimes (as you seem to be aware of) diagnostic reports include too much data and the system doesn't openly communicate to the user what is actually included. I'm glad your system is not of that type.
So my inclination towards not sending general type of diagnostic report is mostly dystopian-ethical.
0 -
HI @veriik,
Locking animation seems to running constantly though when the application window is in the foreground
That's intentional but what's not intentional is the super-high CPU usage, we can't reproduce it. The GPU shouldn't even kick in either. We'll look again, we can't reproduce this on our own machines.
Wouldn't it be more beneficial to initiate animations only when there is some action in the application window?
There's not much actions you can do within the lock view, the only event we can do is active or inactive window. For consistent experience, we want the spinning to start when you're looking at 1Password and to stop when you're not. That is what we did, turned it off when it is inactive.
About diagnostic reports: It's hard or impossible to know how the report is stored and analyzed.
We certainly don't want you to feel unease about this:
- We log our internal 1Password data to
%LOCALAPPDATA%\1Password\logs. We only keep up to 14 days worth, everything else is trashed. - When running the diagnostics report, it'll capture; the current list of running tasks, 1Password settings, browser extensions and their versions, your public 1Password account settings and/or 1Password vaults; their locations and backups, and all Windows errors that mentions 1Password or .NET crashes that uses our 1Password files via Event Viewer.
- We ask users to submit crash report as opt-in for stable builds when they restart app and it is automatic for betas builds. They're trashed after it is submitted. They're stored in
%LOCALAPPDATA%\1Passwords\logs\events - Installer-related logs are stored in
%LOCALAPPDATA%\1Passwords\logs\setup - All internal debug functions are disabled by default and cannot log to any public files. If we need to investigate more thoroughly, we'll work with the customer with specific debug builds we send them or if it is a specific area, we can enable some extra logs via 1Password console and use commands in there.
- Anything related to secrets or stuff is absolutely no-no for us. We never have a single need for this, we won't ask and it will never be allowed to be collected in any form.
We have a privacy policy as well: https://support.1password.com/1password-privacy/
I'll see if I can get the web team to document this for all 1Password apps for our knowledge base.
0 - We log our internal 1Password data to
