Opened 7 years ago

Closed 3 years ago

#10432 closed defect (fixed)

Sudden spike in memory consumption

Reported by: ln5 Owned by:
Priority: Medium Milestone: Tor: 0.2.5.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-auth, mem, tor-03-unspecified-201612
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I see a directory authority dying on out-of-memory. It's running This happened after it had been running for about a week. It died shortly after publishing a consensus, at hh:01:40 with a 'Out of memory on malloc(). Dying.'

Plotting RSS every 10 minutes the last couple of hours shows this:

I'll collect more data and also try to get date and time of the data points.

Child Tickets

Attachments (1)

Rplots.pdf (159.4 KB) - added by ln5 7 years ago.
VSZ and RSS 2013-12-23 -- 2014-01-05

Download all attachments as: .zip

Change History (7)

Changed 7 years ago by ln5

Attachment: Rplots.pdf added

VSZ and RSS 2013-12-23 -- 2014-01-05

comment:2 Changed 6 years ago by nickm

Keywords: tor-auth mem added
Milestone: Tor: 0.2.5.x-final

What would really help would be some kind of breakdown of where the memory is getting allocated from in the code. dmalloc can tell us that; I don't know if there are better tools.

comment:3 Changed 6 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???
Status: newneeds_information

comment:4 Changed 4 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:5 Changed 4 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:6 Changed 3 years ago by nickm

Milestone: Tor: unspecifiedTor: 0.2.5.x-final
Resolution: fixed
Severity: Normal
Status: needs_informationclosed

I'm going to call this "much more solved than it was in 2013"; we've improved memory restriction a lot since then, particularly in 0.2.5.x.

Note: See TracTickets for help on using tickets.