Opened 7 years ago

Closed 6 years ago

#7019 closed defect (worksforme)

Potential memory leak on 0.2.3.x relays

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


My relays and my dirauth have been routinely getting up into the 1-2GB range after running for a week or two on 0.2.3.x... Seems like a memory leak?

I have yet to valgrind.. The relays are too fast, and my dirauth is on a crazy hardended setup that is hard to change :/.

Child Tickets

Change History (6)

comment:1 Changed 7 years ago by arma

Keywords: tor-relay added

comment:2 Changed 7 years ago by arma

It is very unlikely to be a memory leak, given past history.

It's much more likely to be memory fragmentation and/or glibc bugs where it doesn't reclaim freed space.

Not that that helps track it down much.

comment:3 Changed 7 years ago by nickm

Starting with which version? Does relinking with a different malloc help?

comment:4 Changed 7 years ago by arma

see also #5337, which is effectively a duplicate

comment:5 Changed 6 years ago by arma

should we close this one? seems like this ticket appears periodically, and has the same issues, and gets closed after a while for the same reasons.

comment:6 Changed 6 years ago by nickm

Resolution: worksforme
Status: newclosed

I'm inclined to say that any memleak ticket which is just "memory runs short" with no more information is not going to get fixed without more information than this one has.

Note: See TracTickets for help on using tickets.