Chrome extension sometimes unresponsive & eats hella CPU
Sometimes clicking the 1Password icon in my toolbar does nothing and I note Chrome is eating tons of CPU. This will last for minutes and then sometimes after very long time the 1Password pane finally pops up.
I am on Chrome 18/OS X.
Screen shot (same as attached): http://cl.ly/0w041d1g3j3r2L3p3g3Y
-
1Password_eating_CPU.png
53 KB
Comments are currently closed for this discussion. You can start a new one.
2 Posted by Eric Dobson on 18 Apr, 2012 06:43 PM
Hi Alan,
Thanks for taking the time to contact us.
Could you please open Window > Extensions and tell us what version of the 1Password extension you have installed?
Do you notice this when browsing any websites in particular, or does it seem random?
What other extensions do have installed in Chrome?
Thanks!
Eric Dobson
AgileBits Support
3 Posted by contact on 18 Apr, 2012 06:50 PM
3.9.3.39399
I haven’t noticed a pattern — if I do, I’ll let you know.
Installed, enabled plugins:
AdBlock
Clearly
Faviconize Google
FlashBlock
Georgify (affects Hacker News)
Gitmarks (affects GitHub)
HTML5 Enabler for YouTube
rapportive
Readabilty
Reddit Enhancement Suite
RSS Subscription Extension (by Google)
The Camelizer
YouTube "Lights Out"
Support Staff 4 Posted by Khad Young on 18 Apr, 2012 06:53 PM
Thanks for writing back, Alan. Please try installing the latest beta version of the 1Password Chrome extension:
https://agilebits.com/extensions/mac/chrome.html?beta=y
We made some improvements since the version you are currently running that I think will help.
Please let me know how it goes.
Khad Young
Forum Choreographer, AgileBits
http://agilebits.com/support
5 Posted by contact on 19 Apr, 2012 04:31 AM
So far, so good — hard to say conclusively, but I’ll let you know if this pops up again.
ajh
6 Posted by Brandt Swindell on 19 Apr, 2012 01:02 PM
Hello Alan,
Thanks for the update! Please do keep us informed of any changes. :)
Cheers!
Brandt
7 Posted by Stephen Kervin on 28 Apr, 2012 04:17 PM
Hi
I have posted about this issue months back and tried the beta. The BETA does the same thing!
Is there is any chance of a fix for this in the pipeline, its becoming so unuseable I might as uninstall the exention as I can never use it. It use 100CPU for over 10 minutes at a time, dozens of a times a day for no reason. Once it starts there is no useing it as the plugin is unresponsive. You can kill the plugin and restart it , but often that requires restarting chrome for everything to be ok again, although you sometimes get away with it.
Its a really annoying problem making the plugin unsuable.
Support Staff 8 Posted by Kyle Swank on 30 Apr, 2012 03:26 PM
Hi Stephen,
We've noticed that this issue tends to happen mostly when users leave Chrome running for long periods of time. As a suggestion for the time being, you can try restarting the browser between usages and this should prevent it from happening.
We'd love to fix this, but when none of us here on the team can reproduce it we have trouble fixing the problem. It seems that only a small number of our users are encountering this problem and that is making it difficult to address.
I've added your discussion to the short list we have going of similar issues. Hopefully we can get back to you both with some more details soon.
Cheers!
Kyle Swank
AgileBits Support
9 Posted by contact on 01 May, 2012 09:24 PM
Yeah, using the beta version, it has still locked up for half a minute recently (with the accompanying CPU spike) when I clicked the 1Password extension icon in Chrome (stable channel, OS X).
It had been a while since the last time it happened, though. Felt like an improvement, but hard to know whether there is truth in that perception :)
ajh
10 Posted by Stephen Kervin on 01 May, 2012 09:43 PM
Hi, thanks for the reply.
I do always leave my machine and browser running , I am a mac user after all :) so match your criteria.
I use a lot of tabs continuously and a restart of chrome is a loss of 5-10 of time as all the tabs reopen and the browser kicks starts itself. I run usually 10-15 tabs of various websites . The persistent websites are google services like gmail and google docs plus Facebook .
Alan: yes I too had hope at first but it "returns quiet soon" :/
Support Staff 11 Posted by Khad Young on 02 May, 2012 12:15 AM
It isn't uncommon to run 10-15 tabs as most of us here do ourselves.
What kind of uptime are you running with in Chrome? Are we talking weeks or just days?
Khad Young
Forum Choreographer, AgileBits
http://agilebits.com/support
12 Posted by Guy Sie on 31 May, 2012 12:24 PM
I am experiencing the same problem for a while now and have been hoping that one of the beta's will make it magically disappear, no luck so far. I live and work through Chrome, so we're talking 2-3 Chrome windows open with a good 30-40 tabs each. And I leave both the computer and Chrome running indefinitely - or at least, for the past half year or so, until the 1password Extension starts eating up 100% of my CPU and I need to force kill Chrome's main program. Force killing the extension's Chrome Worker drives Chrome haywire and makes all the different Chrome Renderers eat up all remaining CPU time.
I realize that I'm in the 0.1% of users who runs Chrome that heavily and keeps the program up that long, but it is a serious problem for me. Recommending me to restart more often won't be much of a solution; nothing else in my workflow hampers working this way except for the 1password extension.
13 Posted by Stu Helm on 31 May, 2012 12:32 PM
Guy,
That is a fair number of Chrome windows and tabs, and you're probably right that you're in a small percentage of our user-base who use Chrome that heavily, that doesn't however mean that the CPU usage bug isn't a problem, we need to fix it for everyone and we're still tracking down the root cause.
Have you tried disabling auto-save by going to the Settings > Logins section of the Chrome extension and unchecking 'Ask to save new Logins'? If you do that you can stills save Login items manually as such:
I'd be interested to know if turning off auto-save helps you at all?
Stu Helm
Agile Crusader
AgileBits
http://support.agilebits.com
http://twitter.com/1Password
14 Posted by Guy Sie on 31 May, 2012 12:38 PM
Thanks Stu, I'll try that!
15 Posted by Stu Helm on 31 May, 2012 12:40 PM
You're welcome, Guy, do let me know how things turn out.
Stu Helm
Agile Crusader
AgileBits
http://support.agilebits.com
http://twitter.com/1Password
16 Posted by Stephen on 31 May, 2012 01:02 PM
Hi
The longer you leave it running the more it happens is my impression. The
more you restart chrome the less it happens.
In answer to the previous question, is its weeks or months. I never close
my browser unless an update requires a reboot.
Another thing I have noticed is its defenitely worse after a sleeping and
waking the machine (mac osx). Is there anyone else out there experiencing
this problem who is either not a mac user or has the problem with out
sleeping the machine. ?
17 Posted by Stu Helm on 31 May, 2012 01:04 PM
Stephen,
I realise that this is the way you work, but that may well be part of the problem, I tend to close all tabs in Chrome and restart it daily, my whole browsing experience is generally better that way.
Could you try the steps I suggested above for Guy, regarding turning off auto-save, and see if that helps you at all.
Stu Helm
Agile Crusader
AgileBits
http://support.agilebits.com
http://twitter.com/1Password
18 Posted by Stephen on 31 May, 2012 01:19 PM
I will certainly try turning off auto-save so see if it makes a difference.
However continuously closing chrome is no way to work or live.
19 Posted by Mike Tselikman on 31 May, 2012 03:35 PM
Hi Stephen,
We agree, it is just that the problem is that there are inactivity bugs in Chrome that affected some extensions, the longer you keep it open or inactive for a long time, something inside Chrome caused some extensions to hanged for a while. Restarting Chrome is the quickest resolution at the moment until Google can fix some more of those bugs.
According to Google/Chromium, they believe they fixed the issue in Chrome Canary 21 or the latest version of Chrome Developer version of 20.
If you don't mind, I'd recommend trying Chrome Dev 20 instead and see if it'll help. This link will take you to the Developer version of Chrome:
https://www.google.com/chrome/intl/en/eula_dev.html?dl=mac
Please let us know how it turns out.
Thanks!
20 Posted by dpw-ct on 25 Jun, 2012 03:56 PM
This comment was split into a new private discussion: Chrome extension sometimes unresponsive & eats hella CPU
Using 1password mac - Error in chrome extension - can't use short cut command "\"
also when I click on key in tool bar and enter master password it does not connect, just counts connecting 1, 2,3 ...
extension version 3.9.4.39499
1 password Version 3.8.19 (build 31419)
Any advice
Brandt Swindell closed this discussion on 25 Jun, 2012 04:05 PM.
contact re-opened this discussion on 26 Jul, 2012 09:49 PM
21 Posted by contact on 26 Jul, 2012 09:49 PM
So, I’m on Chrome 20.0.1132.57 (stable & up-to-date) and this is still happening. This time, I restarted my computer within the last 14 hours, and had maybe 30 tabs (7 of which were those extremely basic Craigslist pages.)
Have people been having success with Chrome Dev channel?
PS, just bought a family pack. Trying to get my mom + siblings all set up with 1Password & Dropbox.
Support Staff 22 Posted by Khad Young on 27 Jul, 2012 03:38 AM
Hey Alan,
Thanks for sharing the 1Password love. We really appreciate it!
While reports from heavy (30+ tabs) to "really heavy" users (50+ tabs) have been pretty bleak for a bit, it appears that Google has improved this in Chrome 21 and resolved it Chrome 22.
By all accounts that we've seen you should not have this problem in Chrome 22, and Chrome 21 may even resolve it for you.
Please let me know how it goes.
Khad Young
Forum Choreographer, AgileBits
http://agilebits.com/support
23 Posted by Risto Hänninen on 15 Aug, 2012 05:40 PM
I have the same problem and it's driving me nuts. I've had it since installing 1Password. OS X 10.7.4. & Chrome Version 21.0.1180.77. Got approximately 30 tabs open.
1Password at some point starts using 100% CPU and does not calm down. Only option is to kill the 1Password extension process in Chrome. I keep my computer running constantly and only close tabs when I'm done with them and only close the browser when I need to restart my computer (only for updates). I restart Chrome only for updates also.
The browser extension and whole 1Password is pretty much unusable for me since I purchased it. Too bad I probably can't get my money back from the Mac App Store due to the browser extension ruining everything as the extension is separate from the main app.
Overall I'm very disappointed in how 1Password works. It's a nice idea, but the user experience is just poor due to bugs like this & few other things I won't get into now.
24 Posted by Mike Tselikman on 15 Aug, 2012 06:44 PM
Hi Risto,
The bugs are in Chrome, not in 1Password. We can't fix this until Google fixes it first. They're saying it should be fixed in Chrome 22 now.
Please try downloading Chrome 22 Dev here: https://www.google.com/chrome/intl/en/eula_dev.html?dl=mac
Hopefully, that'll stop the CPU spikes.
Please let us know if it is fixed or not, so that we can pass the words to Google.
Thanks!
System closed this discussion on 26 Sep, 2012 06:51 PM.