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
  • #297
Closed
Open
Issue created Nov 27, 2014 by Derek Bruening@derekbrueningContributor

sideline thread has no chance to clean up

From [email protected] on April 23, 2010 14:49:38

In debug build DR synchs + terminates our sideline thread prior to calling our exit event so we have no chance to clean up its memory. DR then asserts about leaks if the sideline thread had thread-local memory. DR either needs to call the client exit event even sooner, before the synchall, or should add support for a sideline exit routine.

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=297

Assignee
Assign to
Time tracking