High CPU usage

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install IBA Opt-out extension

What is the expected output? What do you see instead?
Expected result: idle CPU usage.
Observed result: open the Task Manager: IBA Opt-out is using nearly 100% CPU.

What version of the product are you using? On what operating system?
Chrome 21.0.1180.77 beta on Mac OS X 10.7.4.

Please provide any additional information below.

I initially reported this issue in a comment to a Chromium bug:
http://crbug.com/141178#c20

I obtained profiles and crash data -- see that link for detail.

It looks like IBA Opt-out version 1.2 was released today, coinciding with the 
arrival of this problem.

Original issue reported on code.google.com by fja...@gmail.com on 14 Aug 2012 at 10:02

[GoogleCodeExporter]

Also occurring in Chrome 21.0.1180.77 on Windows 7 with IBA opt-out v1.2, but 
CPU usage closer to 50%.

Original comment by prior....@gmail.com on 14 Aug 2012 at 10:30

[GoogleCodeExporter]

same - 21.0.1180.77 , windows 7, with iba plugin, cpu usage is around 50%.
with affinity set browser takes ~80% of a core, IBA process takes ~60% of a core

Original comment by p.cos...@gmail.com on 14 Aug 2012 at 11:00

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

same - 22.0.1229.2, windows 7, IBA 1.2, I also notice quite high IO as well as 
CPU

Original comment by a...@moore.mx on 14 Aug 2012 at 11:03

[GoogleCodeExporter]

Same here with 21.0.1180.77 on Windows 7. Takes about 60% of a CPU core.

Original comment by wimgoddenajax@gmail.com on 14 Aug 2012 at 12:02

[GoogleCodeExporter]

Same experience on OS X 10.8 with Chrome 21.0.1180.77. As soon as I disable IBA 
Opt-out Chrome processor usage returns to normal.

Original comment by jon.free...@gmail.com on 14 Aug 2012 at 12:08

[GoogleCodeExporter]

Same problem after upgrading to IBA 1.2, on OS X 10.8 with Chrome 21.0.1180.77. 
I had to disable the IBA extension to return the CPU usage to normal.

Original comment by cgen...@gmail.com on 14 Aug 2012 at 12:17

[GoogleCodeExporter]

Same problem on Win 8 RTM, both Desktop and Metro UI. IBA 1.2, Chrome 
21.0.1180.77 m.

Original comment by gav...@gmail.com on 14 Aug 2012 at 12:53

[GoogleCodeExporter]

Process explorer shows much of this is IO bound to:

C:\Users\<username>\AppData\Local\Google\Chrome\User Data\Default\Cookies
and
C:\Users\<username>\AppData\Local\Google\Chrome\User 
Data\Default\Cookies-journal

Original comment by a...@moore.mx on 14 Aug 2012 at 12:57

[GoogleCodeExporter]

Seeing the same insanely-high CPU usage on OS X 10.7.4, running Chrome 
22.0.1229.2 dev.

Original comment by ja...@queso.com on 14 Aug 2012 at 1:33

[GoogleCodeExporter]

To clarify more: I started seeing this problem this morning, so it makes sense 
that it coincides with the new release of the plugin today (as mentioned in the 
original bug report). Disabling the extension in Chrome brings the CPU usage 
back down to normal; re-enabling the extension again spikes the CPU usage.

Interestingly, when the IBA Opt-Out extension is installed, I see high CPU 
usage by the Keep My Opt-Outs extension as well -- disabling the IBA extension 
brings the CPU usage for the Keep My Opt-Outs extension back down to normal. I 
don't know how they're related, but they appear to be.

Original comment by ja...@queso.com on 14 Aug 2012 at 1:35

[GoogleCodeExporter]

Same on OS X 10.6.8, Chrome 21.0.1180.77, appeared just today.

Original comment by azhag...@gmail.com on 14 Aug 2012 at 2:16

[GoogleCodeExporter]

Same problem on Win 7 v. 6.1.7601 SP1 Build 7601.
Running Chrome 21.0.1180.77 with IBA Opt-out extension v. 1.2
Problem started overnight August 14 with high idling CPU.
Disabled IBA Opt-out extension and CPU usage immediately returned to normal.

Original comment by Trond.Ha...@gmail.com on 14 Aug 2012 at 3:03

[GoogleCodeExporter]

Confirmed on Mac, 10.8,  21.0.1180.77 and 22.0.1229.2 dev

CPU usage in excess of 240% on a quad-core. Disabling extension solves the 
problem.

Original comment by mwdi...@gmail.com on 14 Aug 2012 at 3:31

[GoogleCodeExporter]

Same here, linux 3.5.1 - built on gentoo.

Interesting to read that there is a problem between: IBA Opt-Out and Keep my 
opt outs... I can confirm that disabling IBA fixes the issue.

Chromium    22.0.1215.0 (Developer Build 147830)
OS  Linux
WebKit  537.2 (Unknown URL@0)
JavaScript  V8 3.12.14

Original comment by Ian.Kuml...@gmail.com on 14 Aug 2012 at 3:35

[GoogleCodeExporter]

Same issue on os x 10.7.4, chrome 21.0.1180.77.  Just noticed it this morning 
and tracked it back to this.

Original comment by kevin.ro...@gmail.com on 14 Aug 2012 at 4:35

[GoogleCodeExporter]

Same issue here. OX 10.6.8 Chrome 21.0.1180.77, Opt out version 1.2

Original comment by jianghai...@gmail.com on 14 Aug 2012 at 4:54

[GoogleCodeExporter]

Same here Ubuntu 12.04 opt out version 1.2

Original comment by mslap...@gmail.com on 14 Aug 2012 at 6:06

[GoogleCodeExporter]

Same, Windows 7 x64, Chrome 21.0.1180.79, app v1.2, CPU up to 45%

Original comment by ben.choj...@gmail.com on 14 Aug 2012 at 9:45

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

While IBA was installed, I had CPU loads of ~50%. However, after uninstall, CPU 
loads are still constantly at ~25% with no pages open, no extensions enabled. 
I've had to resort to Internet Explorer in the meantime so please fix!

Windows 7, Chrome 21.0.1180.679

Original comment by iMichael...@gmail.com on 14 Aug 2012 at 11:03

[GoogleCodeExporter]

High CPU loads relative to normal (1-5% range) CPU usage can be observed, 
coupled with high disk activity. 

The files to which chrome has activity on is as follows:

C:\$LogFile (NTFS Volume Log)
C:\Users\user\AppData\Local\Google\Chrome\User Data\Default\Cookies-journal
C:\Users\user\AppData\Local\Google\Chrome\User Data\Default\Cookies

By disabling the addon the CPU activity and HDD activity goes down to previous 
normal levels. 

Windows 7 Home Premium Version 6.1 Build 7601: SP1
Google Chrome Version 22.0.1229.2 dev-m
IBA Opt-out (by Google) Version 1.2

Thanks!

Original comment by cbr...@gmail.com on 14 Aug 2012 at 11:48

[GoogleCodeExporter]

Same as the others running OSX 10.7.4 with Chrome version  21.0.1180.79 & IBA 
Opt out version 1.2.
Went home from work last night and when i got in this morning the fan in the 
Macbook was going nuts. Killing the IBA Opt out extension via Chrome's task 
manager stops the high CPU usage. Persistent after restart of browser.

Original comment by jest...@gmail.com on 15 Aug 2012 at 12:16

[GoogleCodeExporter]

Reporting high CPU usage from this extension. Windows 7 SP1, Chrome 
21.0.1180.79, v1.2 of IBA Opt Out. Though I am not having high HDD usage. Only 
started seeing it today.

Also confirming it on my CR-48 running 22.0.122.0 dev w/ v1.2 of opt out.

Original comment by sassa...@gmail.com on 15 Aug 2012 at 3:17

[GoogleCodeExporter]

I have the same issue. The extension is using up to 110% CPU.

IBA Opt-out (by Google) Version 1.2
Mac OS X 10.8
Google Chrome Version 22.0.1229.6 dev

Original comment by patrick....@gmail.com on 15 Aug 2012 at 3:27

[GoogleCodeExporter]

Sorry for the trouble. I'll look into this asap

Original comment by eisinger@google.com on 15 Aug 2012 at 6:00

• Changed state: Accepted
• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

version 1.3 should fix this

Original comment by eisinger@google.com on 15 Aug 2012 at 8:20

• Changed state: Fixed

[GoogleCodeExporter]

Fixed here.
Mac OS X 10.7.4.
Chrome 21.0.1180.75

Original comment by c...@submonkey.net on 15 Aug 2012 at 8:41

[GoogleCodeExporter]

This is odd. With version 1.3 IBA Opt-out doesn't go up to 110% CPU usage 
anymore, however Ghostery ( ghostery.com ) does now. And only when IBA Opt-out 
is enabled.

IBA Opt-out (by Google) Version 1.3
Ghostery Version 3.0.0
Mac OS X 10.8
Google Chrome Version 22.0.1229.6 dev

Original comment by patrick....@gmail.com on 15 Aug 2012 at 1:01

[GoogleCodeExporter]

I'm getting the same issue as patrick above. It's no longer using 100% CPU any 
more(but still something like 20%), however Keep My Opt-outs does, but only 
when IBA Opt-out is enabled.

Original comment by benscobi...@gmail.com on 15 Aug 2012 at 1:18

[GoogleCodeExporter]

looks fixed here on both win7 and chromebook

Original comment by sassa...@gmail.com on 15 Aug 2012 at 2:23

[GoogleCodeExporter]

This is terrible! I love Chrome but if it is not fixed I'm no longer going to 
use it! My CPU usage is at 100% unless I kill the IBA. 

Original comment by Jabe...@gmail.com on 16 Aug 2012 at 1:13

[GoogleCodeExporter]

I see this as fixed with v1.3, as well.

And as for comment #32: um -- a little perspective. (1) It's fixed, in v1.3, so 
far as everyone is reporting. (2) This problem isn't Chrome's fault, it's a 
problem with an extension that nobody's forcing you to run.

Original comment by ja...@queso.com on 16 Aug 2012 at 1:19

[GoogleCodeExporter]

I've had issues similar to this before when chrome got a too big memory 
footprint. Excessive harddrive activity and unresponsive system.

@33:
Thats very rude and also wrong.
There was an update to chrome that caused this bug and it is still in chrome. 
This extension only worked around the bug that is in chrome.

The advertising companies never asked if they could track you but they did 
anyway. So you have to go out of your way to make them not track you and 
violate your personal privacy.

They could as well have made it an Opt-in system. But of course no one in their 
right mind would want shady advertising companies to track you. You wouldnt 
want a shady person follow you around in your town and take notes and pictures 
and sell that info to shady companies that will do bad things with it, now 
would you ?

So yes if you value your privacy you are forced to use extensions like this one.

That take up space and cpu time because the laws havent caught up with the 
illegal privacy violators of the internet and because they hide in countries 
with outdated, corrupt and perverted law systems such as america.

Original comment by laboboL...@gmail.com on 16 Aug 2012 at 10:32

[GoogleCodeExporter]

Issue 23 has been merged into this issue.

Original comment by eisinger@google.com on 16 Aug 2012 at 12:44

[GoogleCodeExporter]

Issue 24 has been merged into this issue.

Original comment by eisinger@google.com on 20 Aug 2012 at 7:44

[GoogleCodeExporter]

The traffic on the unresponsiveness issue seems to have stopped in August, but 
I still have the problem and I never installed IBA Opt-in.  Did Chrome v 23 fix 
the problem or do others still have it?

Original comment by DavidESc...@gmail.com on 18 Dec 2012 at 2:11

[GoogleCodeExporter]

I still have this problem frequently.

Google worker task will go to 80-90%.

Original comment by phill...@gmail.com on 26 Nov 2013 at 3:35

Attachments:

• [About Version.html](https://storage.googleapis.com/google-code-attachments/google-opt-out-plugin/issue-22/comment-38/About Version.html)

[GoogleCodeExporter]

i was wrong about which task.  it is the Google Chrome Helper.

Original comment by phill...@gmail.com on 26 Nov 2013 at 10:41

Attachments:

• activity.tiff

[GoogleCodeExporter]

I see that every one seems to be having the same issue but will one difference, 
I haven't installed the IBA extension but I still get HIGH CPU usage on the 
Google Chrome Helper Process, The only way I can stop the Process is by killing 
it from task manager.

Version 32.0.1700.77
OS X 10.9.1

My Extensions:
Google Docs 0.5
Hangouts 2014.108.433.1
LastPass 3.0.22
Secure Shell 0.8.25

Original comment by Jwb...@gmail.com on 27 Jan 2014 at 8:41