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

[Shane Kerr]

Jelte,

On Jul 9, 2008, at 18:51 +0200, Jelte Jansen wrote:
>
> 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.

This leak is something like 4K per update, so for most users can be  
ignored (in our case we get an update every minute so this is like 6M  
per day, so we'll either use this patch or disable NSEC3 until we  
actually use it).


FYI, I went ahead and tracked our server's memory growth with 3.1.0  
and with the Subversion version 2476 and found the following:

              3.1.0              svn-r2476
NS    RSS   MB  VSZ   MB    RSS   MB  VSZ   MB
----  --------  --------    --------  --------
ns0a        85       143          49       109
ns0a      1904      1911        1905      1911
ns0a      2038      2045        2053      2060
ns0a      2187      2194        2187      2194
ns0a      2321      2327        2336      2342
ns0a      2469      2476        2469      2476
ns0a      2603      2610        2618      2625
ns0a      2752      2758        2752      2758
ns0a      2886      2892        2900      2907

This is the size of the process, taken each 10 minutes. The growth is  
basically identical (slightly more for the Subversion version, but  
that probably has to do with the actual changes to the zone that we  
are getting).


Apologies for the unnecessary worries! :(

--
Shane