1Password 6 on Mac is Suddenly Really Slow

2»

Comments

  • Roman
    Roman
    1Password Alumni
    edited January 2017

    @bockscar11 - I think something went wrong. You should have received a confirmation.

    I tried to locate your email, but couldn't find one. I searched for the email address you used to sign up for the forum.

    Would you mind sending it again? Hopefully we'll be able to catch it this time. I'm sorry about the hassle!

  • bockscar11
    bockscar11
    Community Member

    @Roman I resent diagnostics as requested to support+forum@agilebits.com (and also support@agilebits.com). Included information referring to your post and also my own license. Have not rcvd any confirmation of receipt (or Support ID #), so I do not know if this matter was ever resolved. I'm going to assume this information I sent was received.

  • AGAlumB
    AGAlumB
    1Password Alumni

    @bockscar11: If you sent it from the same email address you use for your forum account, we never received it. That would explain why you didn't receive an autoresponse from BitBot as well. However, if you used a different address, be sure to check your outgoing mail and spam folders, in case it got stuck sending or receiving. And it may be worth trying again, perhaps with a different account. Please let us know the Support ID you receive so we can get back to you as soon as possible to get things sorted out.

  • bockscar11
    bockscar11
    Community Member
    edited January 2017

    @brenty Just dispatched diagnostics email (from diff email addy) for a THIRD time (support+forum@agilebits.com, support@agilebits.com). I do not understand why this is so difficult. Referencing off incoming mail by timestamp is not unheard of.

  • Roman
    Roman
    1Password Alumni

    @bockscar11 - Incoming seems to be the word of issue here. I can't seem to find any indication your email gets to us. Did you receive a support ID when you sent the diagnostic report from the other email address?

  • rickfillion
    edited January 2017

    @bockscar11 @Roman : it did get to us. TYS-97388-582. Looking over the diagnostics report now.

    ref: TYS-97388-582

  • lifeofguenter
    lifeofguenter
    Community Member

    There definitely seems to be a memory leak. This was a screenshot of when 1password was unbearably slow. After restarting the app it was quicker again, but still unlocking (1password mini/browser extension included) is laggy.

    Can we put some efforts into making this app run smoothly? It should "only" be a password manager, but I agree with others, if its sluggy/laggy it kills the work flow...

  • AGAlumB
    AGAlumB
    1Password Alumni

    @lifeofguenter: I'm not seeing anything like that here. Can you send diagnostics as Kevin suggested? That may give us some insight into what's happening there. Thanks in advance!

  • lifeofguenter
    lifeofguenter
    Community Member

    @brenty I'd be curious how many passwords you have and if you sync with dropbox as well. Already sent my details for diagnostics.

  • AGAlumB
    AGAlumB
    1Password Alumni
    edited January 2017

    @lifeofguenter: Yep! I have vaults syncing with iCloud, Dropbox (just under 1500 items there, which is below average compared to some folks here), and 1Password.com, if that helps. And thanks for letting me know. I'll reply to your email and we can continue to troubleshoot there. :)

    ref: HBK-99726-841

  • rrustema
    rrustema
    Community Member

    Without the hassle of sending in my diagnostics report, could you let us know in general why some users have problems with 1Password being slow? Is it because we do not frequently restart our machine or do we keep too many passwords?

    I have also have the problem as described by the others in this thread.

  • AGAlumB
    AGAlumB
    1Password Alumni

    @rrustema: It's really hard to say "this is why", but in my experience it's often an interaction with other software. That's the cause, with the symptom being sluggish performance, and the solution being a reboot. But for a specific, perhaps more satisfying answer, we'd really need to have more information.

  • rrustema
    rrustema
    Community Member

    Ah, then it makes sense to send in a diagnostics report. I have been upgrading OS X since the first release in 2001 (never a clean install) and along the way might have collected clutter in the Library. Perhaps...

    I just sent it at 14h06, with a reference to this comment in this threat in it.

  • Drew_AG
    Drew_AG
    1Password Alumni

    Thanks, @rrustema!

    I took a quick look in our system, but I didn't find an email from the address from your forum account. Did you receive an automated response from the BitBot assistant? If so, please let us know the ticket ID from that email so we can track your report down and make sure it gets answered as quickly as possible.

  • rrustema
    rrustema
    Community Member
    edited February 2017

    Ah, I need to send it from the same address as I use for this forum? That is an address I never send e-mail from, it is for receiving impersonal e-mail like newsletters, website spam, etc. I have resend it, now from that addres. To support@agilebits.com this time, not support+forum@agilebits.com. With a reference to here.

    And you gave it #HLC-18173-219 as support ID.

  • Drew_AG
    Drew_AG
    1Password Alumni

    Thanks again @rrustema! It doesn't actually matter which email address you use to send us a diagnostics report. But we didn't know the support ID for the original one you sent (maybe you didn't get the automated reply from BitBot?), and didn't know what email address you used, so I tried the one from your forum account just in case you used that one. Also, both support@agilebits.com and support+forum@agilebits.com are fine, we should receive it either way (the "+forum" just helps us connect the dots).

    We definitely received the latest report you sent, and someone will get back to you as soon as possible with more information. We'll keep the conversation going directly via email to avoid complicating things between here and there. Cheers! :)

    ref: HLC-18173-219

  • rrustema
    rrustema
    Community Member

    Hi,

    Any insights about HLC-18173-219 from last month? Has e-mail from support to me been filtered perhaps?

  • AGAlumB
    AGAlumB
    1Password Alumni

    @rrustema: Thanks for checking in. I'm really sorry you haven't heard back yet. I'll look into this and reply to you again via email shortly, but I'm posting this here just so you're aware of this, in case it gets caught in a spam filter or something.

    The short, unsatisfying answer is that it isn't clear that one thing in particular is causing things to slow down on your Mac, but I'll include more details in the email. Thanks again for your patience.

    ref: HLC-18173-219

  • rrustema
    rrustema
    Community Member

    Dear Brent,

    Thank you so much for the 12 steps of things to try you e-mailed me today. I don't which of them did the trick, but it worked. Working under OS X just became so much faster! Thank you! Life in the fast lane!

    Please publish those 12 steps somewhere (here?) so they show up after a quick search for this issue. If only one user benefits from it, it is worth the effort.

  • Drew_AG
    Drew_AG
    1Password Alumni

    That's great news, @rrustema! I'm glad Brent was able to help you with that. Many of the steps he sent you are specific to your setup and refer to things he found in your diagnostics report, so they wouldn't necessarily apply to most customers experiencing slow performance with 1Password.

    Hopefully it continues to work well for you from now on, but if the problem returns, please let us know and we'll investigate further. Thanks! :)

  • AGAlumB
    AGAlumB
    1Password Alumni

    Just to follow up on what rrustemasaid, while I'd love to post all of that here, since it was very specific to his particular setup I wouldn't want to send anyone on a wild goose chance. If anyone runs into a similar issue though, we're here to offer the same personalized support for their situation. Cheers! :chuffed:

This discussion has been closed.