Opened 9 years ago

Closed 9 years ago

Last modified 8 years ago

#3344 closed defect (user disappeared)

valgrind run of Tor exit relay

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: 0.2.3.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: tor-relay
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


attached is the valgrind output of a tor exit relay.

it seems tor is doing well with only minor memory leaks.

Child Tickets

Attachments (1)

tor-valgrind.gz (1.4 KB) - added by cypherpunks 9 years ago.

Download all attachments as: .zip

Change History (9)

Changed 9 years ago by cypherpunks

Attachment: tor-valgrind.gz added

comment:1 Changed 9 years ago by Sebastian

which tor version would that be?

comment:2 Changed 9 years ago by nickm

(Also, if you can, I'd love to see the results of running perf or oprofile on an exit)

comment:3 Changed 9 years ago by arma

Owner: set to arma
Status: newaccepted

Also, what platform is it? It seems the leak is in your glibc (or, as or more likely, you killed your Tor in the middle of a function that was using some heap space and would have freed it when it returned).

comment:4 Changed 9 years ago by arma

Owner: arma deleted
Status: acceptedassigned

zero points for trac

comment:5 Changed 9 years ago by nickm

Milestone: Tor: 0.2.3.x-final

comment:6 Changed 9 years ago by nickm

Resolution: user disappeared
Status: assignedclosed

This looks mostly like libevent stuff or libc-internal stuff. Can't do much more without feedback.

comment:7 Changed 8 years ago by nickm

Keywords: tor-relay added

comment:8 Changed 8 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.