This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.

1PasswordAgent cpu bound

rmangino
edited November 2011 in Mac
Hi,



I am using 1Password (Version 3.8.10 (build 31186)) on Lion (10.7.2). I have the browser extensions installed for Safari and Chrome (which is my main browser).



Whenever I launch Chrome, 1PasswordAgent starts eating up 100% of one my cpus which is enough to slow down my entire machine (I can barely type more than a character or two a second). Killing the agent doesn't help since it automatically restarts.



Any pointers/suggestions would be much appreciated.



All the best,

R

Comments

  • khad
    khad Social Choreographer
    Welcome to the forums, rmangino. I'm sorry that you are having this problem.



    A couple things to try before we delve deeper into the issue:



    It sounds like your 1Password installation may be damaged, which is affecting browser integration. To resolve this:



    1. Download 1Password from our web site:

    http://agilebits.com/downloads

    Click on the "Download Now" button under "1Password 3"

    2. Quit your web browser and 1Password, if it's running

    3. Drag the newly downloaded version of 1Password to the same location as any previous one -- replacing it

    4. Run 1Password at least once and then your web browser



    Your information is stored in a data file separate from the application, so it will not be harmed by this procedure.



    I would also suggest removing and then reinstalling the Chrome extension.



    If you are still having trouble, a change in Chrome 15 is affecting a few extensions, and, unfortunately, there is not a way that we are aware of to fix this apart from one of the following:



    1. Set up a new Chrome profile.



    http://support.agilebits.com/kb/browser-extensions/how-to-create-a-new-google-chrome-profile



    2. Install a newer version of Chrome (16 or later) with a fix included. In most cases, creating a new profile works. For some users, they find that the issue is only resolved once upgrading to Chrome 16.



    http://www.google.com/landing/chrome/beta/



    In extremely rare cases the problem is not resolved until upgrading to Chrome 17.



    http://www.google.com/chrome/intl/en/eula_dev.html?dl=mac



    Please let me know how it goes. I'd love to get this resolved for you.



    Cheers,