[tor-bugs] #24806 [Core Tor/Tor]: LTS branch leaks memory continuously under stress/attack, requires back-port of 0.3.2.8-rc fixes to remain viable

[Tor Bug Tracker & Wiki]

#24806: LTS branch leaks memory continuously under stress/attack, requires back-
port of 0.3.2.8-rc fixes to remain viable
--------------------------+------------------------
 Reporter:  starlight     |          Owner:  (none)
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Milestone:
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------

Comment (by starlight):

 In general agree, though seeing the daemon click up 100MB every hour or
 two while under stress/attack causes me to keep an open mind regarding the
 cause.

 After starting 0.3.2.8-rc the relay was still high rated and initially I
 selected the vanilla scheduler.  Memory consumption climbed steadily until
 the consensus rating dropped, holding since at 1.5GB.  Deactivated all
 local activities that could be an influence and memory increased overnight
 from 1.3GB to 1.5GB regardless.  Since then decided to activate KIST
 scheduler after skimming the paper and a glance at the code.

 Will be interesting to see how it looks the next time rating climbs and
 the HSDIR flag is assigned.  Prepared a LSAN instrumented image to run if
 memory consumption takes another unbounded wander.

 Have observed a couple of apparent circuit-extend attacks and it's
 performing better.  Not seeing crypto thread-pair saturate; seeing no
 'assign_to_cpuworker failed" errors and just one "computer too slow" per
 day with a much lower repeat count.

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