[nsd-users] Memory leak from triggered by notifies?

Jelte Jansen jelte at NLnetLabs.nl
Wed Jul 9 16:51:21 UTC 2008

Hash: SHA1

Jelte Jansen wrote:
> Shane Kerr wrote:
>> On Jul 8, 2008, at 14:34 +0200, Ondřej Surý wrote:
>>>> We see this on both FreeBSD (with 64-bit NSD) and Linux (with both
>>>> 32-bit
>>>> and 64-bit NSD).
>>> You forgot to mention what version(s) do you use.
>> Sorry, this is with 3.0.7 (in production, answering external queries)
>> and 3.1.0 (lab testing only, no queries at all now).
> Hmm, you may be right, though it doesn't seem to be in the notification
> code itself; just a low refresh rate seems to make memory usage grow by
> four bytes if a zone is actually changed.

Ok, as it turns out, the big problem was that nsd-patch wasn't called
often enough. However, I actually did find a small memory leak in a part
of the newer code;

If nsd is compiled with NSEC3 support (by default in the latest release
3.1.0), there is a small memory leak in the slave when a non-NSEC3 zone
is updated.

Attached is a patch for people running into this. Alternatively, you
could use --disable-nsec3 as a build-time configure option. The patch is
also in trunk revision 2744 for people who are using subversion, and
will be in the next patch release (3.1.1).

Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: nsd_nsec3_memory_leak.patch
Type: text/x-diff
Size: 544 bytes
Desc: not available
URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20080709/88380028/attachment.bin>

More information about the nsd-users mailing list