1Password consuming 31% of CPU and 3,000mb memory!

timmc
timmc
Community Member

Hi, Task Manager shows 1Password draining over 30% of my CPU and 3,000mb RAM.
And the app isn't even open! How can I/you reduce this?
I've persevered through a lot of beta issues but this is not acceptable going forward, sorry guys.
Can anyone please explain?
Thanks.!


1Password Version: 6.0.227.0
Extension Version: 4.5.9
OS Version: Windows 10
Sync Type: Not Provided
Referrer: kb-search:cpu performance, kb:undefined, kb-search:cpu performance, kb:undefined, kb-search:cpu

Comments

  • AGAlumB
    AGAlumB
    1Password Alumni

    @timmc: Whoa! That's really odd. I've never seen anything like that before. I don't quite understand why you're saying 1Password isn't running if it's showing up in Task Manager, but it definitely doesn't need that many resources. Please generate diagnostic information and send it to support+windowsbeta@agilebits.com so we can look at the logs to determine exactly what is happening:

    1. Open the main 1Password app
    2. In the Search box, type /log and press Enter
    3. At the top, click Email to send it using your default app
    4. Or manually save the log and attach it to a new email to support+windowsbeta@agilebits.com

    Just be sure to include a link to this forum thread and your username in the email so we can 'connect the dots'. You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here so we can quickly track it down.

    Then make sure you update to the latest version and let us know if the problem persists. You're several updates behind. We'll get to the bottom of this! :)

  • timmc
    timmc
    Community Member

    Hey mate, I sent the log thru just a moment ago. Thanks.

    When i say 1Password isn't running I mean just that. It's not open, i.e in my taskbar as an open app,. however it still shows in task manager. Weird.

    I updated last week, same as every other week so I'm surprised to be several updates behind after only one week.....

  • AGAlumB
    AGAlumB
    1Password Alumni

    When i say 1Password isn't running I mean just that. It's not open, i.e in my taskbar as an open app,. however it still shows in task manager. Weird.

    @timmc: Hopefully it's in the notification area then, perhaps hidden behind the ^ icon. Please let me know if this is not the case!

    The beta is under very active development, so more often than not we have multiple releases per week (sometimes per day), and each one can make a big difference (for instance, the version you were using won't have Autosave, which was added a few days ago!)

    Thanks for sending the logs! It looks like there are a few issues here:

    • Please install the latest beta extension, as it seems as though the one you have is outdated.
    • Please sign into your 1Password Account in the app again. Just open your account in the browser and drag QR code on the unlocked 1Password 6 window. It will fill the details, so you just need to enter your new password.
    • Please let me know what sort of anti-virus/anti-malware app you have running, as it seems to be hijacking 1Password's browser connection (though installing the new beta may make this clearer in 1Password Settings > Options > Browsers > Refused Connection Attempts.

    I think you'll be in much better shape after this, but I want to make sure there aren't any other outstanding issues. I look forward to hearing back from you! :)

    ref: LKP-63762-271

  • timmc
    timmc
    Community Member

    Ok 1Password app is up to date and the extension is too. It's running at about 70mb which is big improvement from the 3,000mb yesterday. Afraid to say i just run with Windows Defender and the 1Password app now shows nothing in the Refused Connection Attempts since the upgrade. I'll keep an eye on things and let you know if anything arises :)

  • AGAlumB
    AGAlumB
    1Password Alumni

    @timmc: Thanks for following up. I'm cautiously optimistic. Be sue to let us know if you experience further issues so we can fix it! :)

This discussion has been closed.