#27813: Tor 0.3.4.8 is leaking memory -------------------------------------------------+------------------------- Reporter: anong | Owner: (none) Type: defect | Status: new Priority: 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 | Parent ID: | Points: Reviewer: | Sponsor: -------------------------------------------------+-------------------------
Comment (by r1610091651@…): Similar story here. After upgrade from 3.3.7 -> 3.4.8, I've noticed that memory usage is erratic. Please consult the image below, showing memory available in green and memory used in blue on a tor dedicate system. [[Image(https://www.dropbox.com/s/5mshoftrnpslima/mem-month.png?dl=1)]] The upgrade to 3.4.8 took place on Saturday in week 37. The connection count / load was relativity stable: [[Image(https://www.dropbox.com/s/ojq6dhwi0hcdis0/torconns- month.png?dl=1)]] (green inbound, blue outbound) I was wondering if there were any changes from 3.3.7 to 3.4.8 which might impact memory behaviour on a middle-relay. I'm also wander what is the "source" of this usage? Potentially relevant config entries (remainder is port/ip, accounting & exit(no)): MaxConsensusAgeForDiffs 4 hours DirCache 0 MaxMemInQueues 64 MB (but "defaulting" to 256mb now) Os: Ubuntu 16.04.5 LTS -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27813#comment:7> 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