Opened 7 years ago

Last modified 17 months ago

#6613 assigned defect

[CHROME] Abnormal CPU usage w/ Keep MORE|MY opt-outs installed

Reported by: cypherpunks Owned by: dtauerbach
Priority: Medium Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version: unspeficied
Severity: Normal Keywords: cpu usage resources hang
Cc: kjd Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

With Chrome 21 the HTTPS Everywhere extension process will sporadically start to consume 100% of one core on my 10.8.0 Mac. Quitting Chrome does not usually solve the problem, but killing the extension's process does for a while. I eventually disabled the extension.

Child Tickets

Change History (16)

comment:1 Changed 7 years ago by pde

Component: HTTPS Everywhere: ChromeEFF-HTTPS Everywhere
Summary: Abnormal CPU usage in Chrome HTTPS Everywhere extension[CHROME] Abnormal CPU usage

What version of HTTPS Everywhere was this? Is it still happening?

comment:2 in reply to:  1 Changed 7 years ago by kjd

Replying to pde:

What version of HTTPS Everywhere was this? Is it still happening?

I am not the original ticket reporter, but I have the same issue since installing HTTPS Everywhere version 2012.10.18 within the past month. I am using Chrome version 22.0.1229.94 on Windows 7. The problem started around the time I installed HTTPS Everywhere, and this is the only extension I have installed within the last 6 months (see below for a list of my other extensions).

I don't know what triggers the issue, but after using Chrome for a short time (maybe 10-30 minutes), it uses 100% of one CPU core.

If I close Chrome when I see the issue occur (laptop fan kicking into high speed is one way I notice the issue occurring), Chrome closes fine and I can restart Chrome and use until the problem happens again.

If I don't close Chrome within a short time of the issue occurring, I can't close Chrome and must kill it with the Windows task manager.

I am using a few other extensions:

  • AdBlock Plus 1.2
  • IETab Classic 0.9.8
  • Incredible Start Page 1.6.2
  • Keep MORE Opt Outs 1.0.0
  • Reddit Enhancement Suite 4.1.3

comment:3 Changed 7 years ago by pde

Cc: kjd added
Version: HTTPS-E 3.0development.5unspeficied

One diagnostic that might be useful would be checking to see that HTTPS Everywhere isn't doing a large amount of anything. In Chrome, you can generally see what it's up to do by going to the about:extensions page, making sure you're in Developer mode, and in the HTTPS Everywhere section, clicking on "Inspect views: _generated_background_page.html".

comment:4 Changed 7 years ago by pde

Priority: normalmajor

comment:5 Changed 7 years ago by pde

Priority: majorcritical

I have been able to reproduce this with Chromium 21 on linux with the same set of extensions installed that kjd mentions above. Thus far, I haven't been able to get a repro with disjoint subsets of those extensions, but I probably haven't tried for long enough.

comment:6 Changed 7 years ago by pde

I spoke to soon. Successful reproduction with ABP + HTTPS-E + KMOO + Reddit.

comment:7 Changed 7 years ago by pde

A decent attempt at reproducing with ABP + HTTPS-E + KMOO has shown some high CPU usage (30-50%) but not seemingly not the same thing as previously, which caused 100% usage of one core plus lockups in things like the "inspect active views" developer console.

comment:8 Changed 6 years ago by cypherpunks

I have also been having trouble with this issue on various Windows versions of Chrome. As well as high CPU usage (25%-40%), memory use and I/O increase massively. In fact, memory use seems to just keep on increasing until I kill the offending Chrome process.

I also have ABP, but not Keep More Opt Outs (though I DO have the basic 'Keep My Opt Outs'). The problem persists if ABP is disabled, but so far no sign of it with KMOO off.

comment:9 in reply to:  description Changed 6 years ago by kjd

Replying to cypherpunks:
I was able to reproduce with only the extenstions "HTTPS Everywhere" and "Keep MORE Optouts" enabled. The base Chrome process is using a lot of CPU, the HTTPS Everywhere and Keep MORE Optouts are also using significant CPU. This occurred while Chrome was running in the background with one tab open to my GMail inbox. I have a screenshot of the Chrome Task Manager if you need it, although it doesn't show much more information.

comment:10 Changed 6 years ago by pde

Summary: [CHROME] Abnormal CPU usage[CHROME] Abnormal CPU usage w/ Keep MORE|MY opt-outs installed

Interesting. It looks as though either Keep {MORE|MY} Opt Outs can trigger the problem. I was using Keep MY when I reproduced beforehand; Keep MORE triggered it very quickly just now.

It looks to me as though the problem could be the two extensions fighting over what exact cookies 3rd party tracking sites get to define. HTTPS-E wants to turn on the secure flag in those cookies and KMOO thinks the cookies are being deleted and decides to recreate them.

AdBlock plus probably makes the problem less severe, especially if you use EasyPrivacy, because it will stop more of these cookies from being set in the first place.

comment:11 Changed 6 years ago by pde

There's a thread with more information about this here:

https://mail1.eff.org/pipermail/https-everywhere/2012-November/thread.html

comment:12 Changed 6 years ago by pde

Owner: changed from pde to dtauerbach
Status: newassigned

comment:13 Changed 6 years ago by dtauerbach

I was able to reproduce two phenomena separately: first, CPU becoming very high; second, infinite loop regarding setting cookies. The infinite loop shows up in the console, here's an example:

KMOO:

Unlocking name:uuid2domain:.adnxs.com KMOO.js:200

  • Checking removed cookie uuid2 from .adnxs.com (

Object
) KMOO.js:200

  • Valid opt-out cookie uuid2 was removed from .adnxs.com; recreating in 5s KMOO.js:200
  • Locking name:uuid2domain:.adnxs.com KMOO.js:200
  • Checking changed/added cookie uuid2 from .adnxs.com (

Object
) KMOO.js:200

  • Valid opt-out cookie uuid2 was added to .adnxs.com. KMOO.js:200
  • Unlocking name:uuid2domain:.adnxs.com KMOO.js:200
  • Checking removed cookie uuid2 from .adnxs.com (

Object
)
[snip]

HTTPS E:

Securing cookie uuid2 for .adnxs.com, was secure=false util.js:7
Applicable rules for .adnxs.com: util.js:7

AppNexus util.js:7

Securing cookie uuid2 for .adnxs.com, was secure=false util.js:7
Applicable rules for .adnxs.com: util.js:7

AppNexus util.js:7

Securing cookie uuid2 for .adnxs.com, was secure=false

However, this loop doesn't seem to be causing very high CPU load in the present case -- note the 5 second wait. When high CPU was experienced, I had to shut down Chrome before I could get useful logs. Not sure if the two issues are related or not, need to investigate more.

System specs:
Linux (Ubuntu 12.04)
Chrome 26.0.1397.2 dev
HTTPS Everywhere 2013.1.18
Keep More Opt-Opts 1.0.0

comment:14 Changed 6 years ago by dtauerbach

I'm now having trouble reproducing the abnormal CPU usage with only these two extensions. The cookie re-writing fight is reproducible but does not lead to high CPU load. I am going to try turning on ABP and Reddit to attempt to reproduce the CPU issue.

comment:15 Changed 5 years ago by jsha

Priority: criticalnormal

comment:16 Changed 17 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

Note: See TracTickets for help on using tickets.