Profile-driven work to reduce memory usage, focusing on clients and mobile.

changed milestone to %Tor: 0.4.0.x-final

added 035-roadmap-master 035-triaged-in-20180711 component::core tor/tor milestone::Tor: 0.4.0.x-final priority::medium resolution::implemented severity::normal sponsor19 sponsor::8-must status::closed type::defect labels

Trac:
Keywords: N/A deleted, 035-triaged-in-20180711 added

We've done a fair bit of this, especially the children of #27243 (moved); more can come in 0.3.6.

Trac:
Milestone: Tor: 0.3.5.x-final to Tor: 0.3.6.x-final

Trac:
Sponsor: Sponsor8-must to Sponsor19-must

Tor 0.3.6.x has been renamed to 0.4.0.x.

Trac:
Milestone: Tor: 0.3.6.x-final to Tor: 0.4.0.x-final

I'm moving this ticket back to sponsor8, for the same reason as I moved #21814 (moved).

This change doesn't mean anything about whether we should do it, just about whether it is critical-path to getting the anticensorship team back up and going.

Trac:
Sponsor: Sponsor19-must to Sponsor8-must

(We already did a great deal of work here, though we might want to squeeze a little more in for #28481 (moved).)

Yes. This one will not fit in sponsor 8 work. And #28020 (moved) shows improvement.

Trac:
Sponsor: Sponsor8-must to Sponsor19

We have done as much of this as we can for sponsor8; we should open a new ticket for sponsor19 if we decide to do more on this task there.

Trac:
Status: new to closed
Sponsor: Sponsor19 to Sponsor8-must
Resolution: N/A to implemented

Yes. That sounds fine. I'm adding a keyword to the ticket as a reminder.

Trac:
Keywords: N/A deleted, sponsor19 added

closed

mentioned in issue #27243 (moved)

mentioned in issue #28481 (moved)

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