Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 577
    • Issues 577
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 117
    • Merge requests 117
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container 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
  • ISC Open Source ProjectsISC Open Source Projects
  • BINDBIND
  • Issues
  • #3051
Closed
Open
Issue created Dec 08, 2021 by Ondřej Surý@ondrejOwner

Missing destroy(s) for rwlocks, mutexes and conditions

It was reported to us that there's a runaway memory leak on FreeBSD which was identified as missing dtor for pthread primitives:

  1. sock->cond in netmgr - the one causing runaway memory use
  2. worker->lock - one per worker
  3. rwlocks in db.c and dlz.c - initialized once per named (fixing would require dtor at library unload, not worth fixing)
  4. rwlock in lib/*/result.c - initialized once per named (fixing would require dtor at library unload, not worth fixing)
Assignee
Assign to
Time tracking