#27813: Tor 0.3.4.8 is leaking memory
-------------------------------------------------+-------------------------
 Reporter:  anong                                |          Owner:  (none)
     Type:  defect                               |         Status:
                                                 |  needs_information
 Priority:  Very High                            |      Milestone:  Tor:
                                                 |  0.3.5.x-final
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  0.3.4.8
 Severity:  Critical                             |     Resolution:
 Keywords:  regression? memleak oom              |  Actual Points:
  034-backport tor-relay 035-must                |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by Christian):

 Replying to [comment:20 arma]:
 > What's in your torrc? Can you simplify it to the point that it's super
 simple, yet you still experience this problem?

 I didn't touch torrc in a long time, except now for adding and tweaking
 `MaxMemInQueues`:


 {{{
 $ grep ^[A-Z] /etc/tor/torrc
 SOCKSPort                 0
 Log                       notice file /var/log/tor/notices.log
 RunAsDaemon               0             # SystemD needs this to be 0
 DataDirectory             /var/lib/tor
 ControlPort               9051
 HashedControlPassword     xxxx
 ORPort                    9001
 Nickname                  foobar
 RelayBandwidthRate        1024 KBytes
 RelayBandwidthBurst       1536 KBytes
 AccountingStart           week 1 00:00
 ContactInfo               XXX
 DirPort                   9030
 MyFamily                  $xxxx, $xxxx
 ExitPolicy                reject *:*
 ExitRelay                 0
 DisableDebuggerAttachment 0
 MaxMemInQueues            256 MB
 }}}

 I haven't had a OOM-killing in two days now and I like to imagine that
 switching from `zram` to `zswap` magically helped, maybe. I tried running
 `tor` under `Valgrind` but don't don't know if I did it right and it
 didn't report any leaks:

 {{{
 ==1697== Command: /usr/bin/tor -f /etc/tor/torrc --pidfile
 /var/run/tor/tor.pid --log notice\ file\ /var/log/tor/tor.log
 --runasdaemon 1 --datadirectory /var/lib/tor --user tor
 [...]
 ==1699== LEAK SUMMARY:
 ==1699==    definitely lost: 0 bytes in 0 blocks
 ==1699==    indirectly lost: 0 bytes in 0 blocks
 ==1699==      possibly lost: 864 bytes in 3 blocks
 ==1699==    still reachable: 34,118 bytes in 206 blocks
 ==1699==         suppressed: 0 bytes in 0 blocks
 }}}

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

Reply via email to