Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D dynamorio
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,467
    • Issues 1,467
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 44
    • Merge requests 44
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • DynamoRIO
  • dynamorio
  • Issues
  • #4418
Closed
Open
Issue created Aug 25, 2020 by Derek Bruening@derekbrueningContributor

Support -vmheap_size > 2G

Today, simply due to using the same static bitmap size for both vmcode and vmheap, we limit -vmheap_size to 2G. We would like to allow increasing its size, to avoid things like #2115, to allow using guard pages with larger page sizes (xref #4415).

Xref #2115: beyond-vmheap slowdowns allocating memory Xref #3570 on -vm_size 2G Xref #4415 on parceling out sub-page pieces

Assignee
Assign to
Time tracking