[tor-bugs] #10281 [Applications/Tor Browser]: Investigate usage of alternate memory allocators and memory hardening options

[Tor Bug Tracker & Wiki]

#10281: Investigate usage of alternate memory allocators and memory hardening
options
-------------------------------------------------+-------------------------
 Reporter:  mikeperry                            |          Owner:
     Type:  enhancement                          |         Status:  new
 Priority:  High                                 |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tbb-security, tbb-hardened,          |  Actual Points:
  TorBrowserTeam201609                           |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
                                                 |  SponsorU
-------------------------------------------------+-------------------------

Comment (by gk):

 I backported the patch from
 https://bugzilla.mozilla.org/show_bug.cgi?id=1277704 (and previous related
 patches) and ran a try build with them based on ESR45:

 https://treeherder.mozilla.org/#/jobs?repo=try&revision=7a567af3611e

 There is a lot of test bustage visible. But if one compares that to a
 vanilla ESR45 build

 https://treeherder.mozilla.org/#/jobs?repo=try&revision=d3fa3b49cda3

 then it seems to me the test bustage is not related to enabling jemalloc4.
 Moreover, (intermittent) test failures related to jemalloc 4.2.1 were
 reported for x86-64 win which we don't support currently. Thus, I think
 for the alpha series it could make sense to backport 4.2.1 and start
 playing with hardening it.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10281#comment:29>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online