search

ashelybeth / google-opt-out-plugin

Automatically exported from code.google.com/p/google-opt-out-plugin
1 stars 0 forks source link

100% CPU usage #24

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Just enable this extension in my several environments.

What is the expected output? What do you see instead?

chrome main process use 100% CPU by busy loop.

What version of the product are you using? On what operating system?

Linux (64-bit & 32-bit userland Debian unstable)

Please provide any additional information below.

From some days(?) ago, when I enable this extension I got 
Google chorme main process exhaust cpu usage. By disabling
this extension CPU usage go down to normal.
I hit this issue on my two machines.

I check main process with strace; it seems infinite loop
on retring to read from socket with err (EAGAIN).

Original issue reported on code.google.com by tatsuki....@gmail.com on 20 Aug 2012 at 4:39

GoogleCodeExporter commented 8 years ago 
What version of the plugin are you using?

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

GoogleCodeExporter commented 8 years ago 
version 1.4 from chrome web store.

Original comment by tatsuki....@gmail.com on 20 Aug 2012 at 7:24

GoogleCodeExporter commented 8 years ago 
and you still see 100% CPU usage with version 1.4?

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

GoogleCodeExporter commented 8 years ago 
ouch I forgot to write the version of chrome; 20.0.1132.57 & 21.0.1180.79 beta.

Original comment by tatsuki....@gmail.com on 20 Aug 2012 at 7:33

GoogleCodeExporter commented 8 years ago 
> and you still see 100% CPU usage with version 1.4?

Oh? Now it seems resolved!?
Curretly I can NOT reproduce the issue on my both environments.

Why?
When I wrote this ticket, I certainly hit the problem.
Is this server-side problem?

Original comment by tatsuki....@gmail.com on 20 Aug 2012 at 7:39

GoogleCodeExporter commented 8 years ago 
The problem existed in 1.2 and 1.3, 1.4 fixed it

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

GoogleCodeExporter commented 8 years ago 
Hmmm. 
In first, I'm sorry about I forget to check old duplicated ticket.
And I guess I report this before update. Actually I didn't confirm
the version of plugin.

Anyway thank you for your time!

Original comment by tatsuki....@gmail.com on 20 Aug 2012 at 7:51