controller: GETINFO stats to expose OOM details

Our OOM handler keeps track of lots of memory-consumers. We could expose that info to the controller.

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified owner::yawning parent::17284 points::.3 priority::medium severity::normal sponsor::S-can status::assigned tor-control type::enhancement labels

Trac:
Sponsor: N/A to SponsorS-can
Keywords: N/A deleted, tor-controller-extension added
Type: defect to enhancement
Milestone: N/A to Tor: 0.2.9.x-final
Component: - Select a component to Core Tor/Tor

Taking this for 0.2.9

Trac:
Status: new to assigned
Owner: N/A to yawning

Hi, Yawning! I'm deferring these tickets assigned to you from 0.2.9 to 0.2.???, since you're going to be out for September. But if you wind up wanting to do any of them for 0.2.9 anyway, please feel free to move them back.

(This is my ticket-deferring afternoon)

Trac:
Keywords: N/A deleted, nickm-deferred-20160905 added
Milestone: Tor: 0.2.9.x-final to Tor: 0.2.???

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: nickm-deferred-20160905 deleted, N/A added

Unify tor-controller-extension keyword to "tor-control".

Trac:
Keywords: tor-controller-extension deleted, tor-control added

changed time estimate to 2h 24m

moved to tpo/core/tor#19319 (closed)