update jemalloc?

Do we want to update to a newer jemalloc for TBB/ESR52?

added component::applications/tor browser ff52-esr owner::tbb-team priority::medium resolution::wontfix severity::normal status::closed type::enhancement labels

Getting this on our radar for alpha release in less than two weeks.

Trac:
Keywords: tbb-7.0-must deleted, tbb-7.0-must-alpha added

Actually, this is currently an alpha-only feature. Therefore, this should be lesser prio.

Trac:
Keywords: tbb-7.0-must-alpha, TorBrowserTeam201704 deleted, N/A added
Type: defect to enhancement

We don't want to update jemalloc4. Actually, we'll remove it as Mozilla won't ship it and the tiny bit of defense we currently use is gone upstream.

Trac:
Resolution: N/A to wontfix
Status: new to closed

For esr52 cycle it is possible to use jemalloc4, updated to 4.5 at least or later, or you are going to use better approaches?

Replying to cypherpunks:

For esr52 cycle it is possible to use jemalloc4, updated to 4.5 at least or later, or you are going to use better approaches?

It's not sure yet what we are going to use. https://bugzilla.mozilla.org/show_bug.cgi?id=1052573 sounds interesting, though.

Replying to gk:

Replying to cypherpunks:

For esr52 cycle it is possible to use jemalloc4, updated to 4.5 at least or later, or you are going to use better approaches?

It's not sure yet what we are going to use. https://bugzilla.mozilla.org/show_bug.cgi?id=1052573 sounds interesting, though. Have they decided to improve mozjemalloc with it (and abandon jemalloc4), but do nothing for mingw?

closed

moved to tpo/applications/tor-browser#21852 (closed)