Teach the OOM handler about the DNS cache

changed milestone to %Tor: 0.3.5.x-final

added 035-triaged-in-20180711 component::core tor/tor dns milestone::Tor: 0.3.5.x-final oom points::1 priority::medium resolution::implemented reviewer::nickm severity::normal sponsor::V-can status::closed tor-dos tor-relay type::enhancement labels

Trac:
Type: defect to enhancement
Component: - Select a component to Tor

Trac:
Owner: N/A to nickm
Status: new to accepted

Trac:
Keywords: N/A deleted, tor-dos added

Trac:
Points: small to 1

Trac:
Parent: N/A to #17293 (moved)

by no means sure that I can get to these.

Trac:
Status: accepted to assigned
Owner: nickm to N/A

Put all unowned "assigned" tickets back into "new".

Trac:
Status: assigned to new

Trac:
Milestone: Tor: 0.2.9.x-final to Tor: 0.2.???

Trac:
Sponsor: SponsorU-can to N/A

Unparenting these from #17293 (moved); holding for future work.

Trac:
Parent: #17293 (moved) to N/A

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

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

Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Keywords: tor-dos deleted, tor-dos oom tor-relay dns added

Trac:
Sponsor: N/A to SponsorV-can

Trac:
Cc: N/A to neel@neelc.org

My PR is available here: https://github.com/torproject/tor/pull/223

What I do for the OOM handler in this PR is that I clear the cache with purge_expired_resolves() with now as the current time, and increase the interval by an hour until either we cleared enough memory or there are no more entries.

Trac:
Status: new to needs_review
Milestone: Tor: unspecified to Tor: 0.3.5.x-final