Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
BIND
BIND
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 585
    • Issues 585
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 112
    • Merge Requests 112
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #1903

Closed
Open
Opened Jun 01, 2020 by Michal Nowak@mnowakMaintainer

Authoritative server leaks 260 KB every 1-2 hours

I run stress test against BIND 9.16.3 authoritative server on Alpine Linux 3.12 (uses MUSL libc) for 18 hours and I noticed that in many cases named's VSZ usage bumps 260 bytes every 1-2 hours. I haven't spotted this on Linux distributions with glibc. There are a few discrepancies from the "260 byte rule", but it seems too regular to be a coincidence. Although the mem usage bump is really tiny, there might be a leak of structure.

named-memory-use-graph-alpine-3.12

Here are VSZ/RSS data every 30 seconds: alpine-vm.txt

Here's a sample of few last lines funneled via uniq:

...
422496
422756
423016
423276
423536
423796
424056
424316
424576
424836
425096
425356
425616
425876
Edited Jun 02, 2020 by Michal Nowak
Assignee
Assign to
BIND 9.17 Backburner
Milestone
BIND 9.17 Backburner
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/bind9#1903