Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #27985

Closed (moved)
(moved)
Open
Created Oct 09, 2018 by Trac@tracbot

Memory leak with Tor 0.3.4.8-1 and Linux 4.18.12.a-1-hardened

Hi,

one of my nodes running Tor 0.3.4.8-1 and Linux 4.18.12.a-1-hardened has a heavy memory leak, which is related to Tor, but it does not show up on top that it is Tor causing this. I just found out by restarting services with "good luck" that it's Tor causing this.

This is what the memory leak looks like: https://imgur.com/a/h4bzyhy

When oom_reaper killed Tor, it printed:

Oct 08 22:52:25 zepto.mcl.gg kernel: Out of memory: Kill process 2392 (tor) score 27 or sacrifice child Oct 08 22:52:25 zepto.mcl.gg kernel: Killed process 2392 (tor) total-vm:1405252kB, anon-rss:888384kB, file-rss:0kB, shmem-rss:0kB Oct 08 22:52:25 zepto.mcl.gg kernel: oom_reaper: reaped process 2392 (tor), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

oom_reaper also killed a lot of processes before Tor, because even my Kernel seemed to be unsure where that memory usage came from. As I said, it does not appear as VIRT, RES or even SHR.

Only notable changes to torrc is to listen on the docker if (SocksPort 172.17.0.1:9050) and MaxCircuitDirtiness 120.

I'd be very happy if somebody could help troubleshooting this, thanks.

Trac:
Username: wrmsr

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking