Prop278: Establish an upper-bound for LZMA2 memory usage

Our initial analysis shows that LZMA2 can be quite a memory hog, which means we should establish some sort of upper-bound for its memory usage and how we can actually enforce it.

changed milestone to %Tor: 0.3.1.x-final

added TorCoreTeam201703 actualpoints::0.2 component::core tor/tor milestone::Tor: 0.3.1.x-final owner::ahf points::3 priority::medium prop278 resolution::fixed severity::normal sponsor::4 status::closed type::task labels

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

Trac:
Keywords: N/A deleted, TorCoreTeam201703 added

Add prop278 keyword.

Trac:
Keywords: N/A deleted, prop278 added

(unparenting this ticket)

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

Patch for adding an upper bound for LZMA decoding can be found at https://gitlab.com/ahf/tor/merge_requests/7/

Trac:
Status: accepted to needs_review
Actualpoints: N/A to 0.2

Looks good. I had a couple of questions on the ticket.

Trac:
Status: needs_review to merge_ready

Answered one question, asked another on the merge request.

Want a follow-up commit on this branch where we rename our LZMA option to x-tor-lzma before we merge?

sure!

merged and renamed it to x-tor-lzma.

Trac:
Resolution: N/A to fixed
Status: merge_ready to closed

closed

changed time estimate to 24h

added 1h 36m of time spent

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