[tor-bugs] #5362 [Tor Client]: If StrictExitNode is set to 1 tor start using 100% cpu after a few minutes

[Tor Bug Tracker & Wiki]

#5362: If StrictExitNode is set to 1 tor start using 100% cpu after a few minutes
---------------------------+------------------------------------------------
    Reporter:  Phoenix87   |       Owner:                    
        Type:  defect      |      Status:  reopened          
    Priority:  normal      |   Milestone:  Tor: 0.2.2.x-final
   Component:  Tor Client  |     Version:  Tor: 0.2.2.35     
  Resolution:              |    Keywords:                    
      Parent:              |      Points:                    
Actualpoints:              |  
---------------------------+------------------------------------------------

Comment(by nickm):

 Oh hey, if you're on Linux, this should be pretty easy to track down with
 profiling: just run Tor under 'perf', and see where the cycles are spent.
 To do this, just run "perf record tor (options)" instead of "tor
 (options)".  Once the CPU has spiked for a while, exit Tor, then use "perf
 report > output" to get a breakdown of where Tor is spending its time.
 (I'd do this myself, but I can't make the bug happen: I just tried for
 about 20 minutes to reproduce with the current maint-0.2.2 branch on my
 computer, and didn't get any weird CPU issues.)

 (BTW, as far as I can tell, "UK" isn't likely to work... the maxmind geoip
 database thinks that the country code in question is "GB".)

 Also, is this

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5362#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online