[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #6613 [EFF-HTTPS Everywhere]: [CHROME] Abnormal CPU usage w/ Keep MORE|MY opt-outs installed

#6613: [CHROME] Abnormal CPU usage w/ Keep MORE|MY opt-outs installed
--------------------------------------+-------------------------------------
 Reporter:  cypherpunks               |          Owner:  dtauerbach 
     Type:  defect                    |         Status:  assigned   
 Priority:  critical                  |      Milestone:             
Component:  EFF-HTTPS Everywhere      |        Version:  unspeficied
 Keywords:  cpu usage resources hang  |         Parent:             
   Points:                            |   Actualpoints:             
--------------------------------------+-------------------------------------

Comment(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

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6613#comment:13>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs