search

shadowkai97 / fauxbar

Automatically exported from code.google.com/p/fauxbar
0 stars 0 forks source link

100% CPU usage after installing fauxbar and restarting Chrome #72

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Install fauxbar, set up some settings
2. Quit Chrome
3. Start Chrome

What is the expected output? What do you see instead?
After starting Chrome the CPU usage jumps to 100% and Chrome becomes 
unresponsive. Only taskkill -f -im chrome.exe helps. I barely could uninstall 
the extention. Even the fauxbar memory helper couldn't help. 

What version of the product are you using? On what operating system?
Chrome 17.0.942.0 dev-m, Windows 7 x64.

Please provide any additional information below.
It would be a cool extention, but the high CPU usage issue makes it unusable.

Original issue reported on code.google.com by bielejew...@gmail.com on 18 Nov 2011 at 5:21

GoogleCodeExporter commented 8 years ago 
Merging into issue #59 - will comment there.

Only seems to happen with Chrome 17.

Original comment by fauxbar....@gmail.com on 19 Nov 2011 at 2:34

GoogleCodeExporter commented 8 years ago 
So if it seems to happen only in Chrome 17 are you going to fix it soon?

Original comment by bielejew...@gmail.com on 19 Nov 2011 at 6:03

GoogleCodeExporter commented 8 years ago 
Please read my comment here for details:
http://code.google.com/p/fauxbar/issues/detail?id=59#c8

In short, I'd love to fix this but I can't reproduce this myself and I'm out of 
ideas, so I need error details from users if possible. It may be a Chrome 
extension API issue that's out of my control, but I can't tell. Chrome Dev 
versions are not always stable.

The link above provides info on how to enable error logging for Chrome. 
Fauxbar's background console (and/or a normal Fauxbar page's console) may also 
contain error messages if you'd like to try looking.

Original comment by fauxbar....@gmail.com on 20 Nov 2011 at 1:42

GoogleCodeExporter commented 8 years ago 
Now I also can't reproduce this error, becouse I've cleaned the history 
(fauxbar said it was 16 000 items), and the problem is gone, everything is nice 
and fast.

Original comment by bielejew...@gmail.com on 20 Nov 2011 at 8:23