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 569
    • Issues 569
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 112
    • Merge requests 112
  • 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
  • #232
Closed
Open
Issue created Apr 26, 2018 by Ghost User@ghost

memory leak patch request for bind 9.11.3

Summary

Current stable version9.11.3 is experiencing significant memory leak. Release notes on your website indicate that this bug was identified as rndc memory leak and addressed in your early deployment version bind9.12.1 Installed 9.12.1 on my test environment and confirmed that memory leak issue is indeed addressed, however I am now experiencing a new bug with 9.12.1 which was reported in https://bugs.archlinux.org/task/57535

Requesting memory leak patch to be downstream to current stable version. Or if you can provide me with the patch to apply it to my system

Steps to reproduce

Please install your current stable version 9.11.3 and load about 500k zones. To reproduce memory leak at faster rate please run a rndc config/reloads on a frequent rate

What is the current bug behavior?

(What actually happens.) memory leak

What is the expected correct behavior?

(What you should see instead.) no memory leak (see your early deployment-version or version 9.9.9)

Relevant configuration files

(Paste any relevant configuration files - please use code blocks (```) to format console output. If submitting the contents of your configuration file in a non-confidential Issue, it is advisable to obscure key secrets: this can be done automatically by using named-checkconf -px.)

same config file is used in 4 different versions and confirmed memory leak got introduced with your 9.10.x series and fixed in your early deployment version 9.12.1

bind9.9.9 - no memory leak bind9.10.0 - memory leak bind9.11.2 - memory leak bind9.11.3 - memory leak bind9.12.1 - no memory leak

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem.) http://ftp.isc.org/isc/bind9/9.12.1/RELEASE-NOTES-bind-9.12.1.html

" rndc reload could cause named to leak memory if it was invoked before the zone loading actions from a previous rndc reload command were completed. [RT #47076] "

Assignee
Assign to
Time tracking