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
  • #4423
Closed
Open
Issue created Aug 27, 2020 by Derek Bruening@derekbrueningContributor

split "Peak vmm blocks" stats into vmcode and vmheap

The stats, esp the rstats, for vmm blocks should be updated to reflect which are in vmcode and which in vmheap, since that split (to be fair, the split was done recently, and the stats were added long long ago) is critical to understanding DR memory pressure:

                          Peak vmm blocks for heap :             14679
                         Peak vmm blocks for cache :              5139
                         Peak vmm blocks for stack :              9039
                  Peak vmm blocks for special heap :              4518
                  Peak vmm blocks for special mmap :              9043
Assignee
Assign to
Time tracking