Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Browser Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 830
    • Issues 830
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor BrowserTor Browser
  • Issues
  • #20998
Closed
Open
Issue created Dec 16, 2016 by Georg Koppen@gkDeveloper

Partition Tor Browser heap with jemalloc

We should investigate performance and robustness of a partitioned heap using jemalloc4. Some links to get started:

http://ggp.name/2014/10/15/Partitioned-heap-in-Firefox-pt1.html http://ggp.name/2015/03/03/Partitioned-heap-in-Firefox-pt2.html

And tjr's summary:

https://lists.torproject.org/pipermail/tbb-dev/2015-October/000309.html

One thing worth considering is whether it should be random partitions or not.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking