Are you sure it is a memory leak, or is it simply the NOTIFICATION-LOG-MIB
implementation?
Does the memory usage still increase when you run with
"--doNotRetainNotificationLogs=yes" or the equivalent in snmptrapd.conf?
Bill
On Tue, Jul 11, 2017 at 3:12 AM, Jeffry Copps <jeffrycopps1...@gmail.com>
wrote:
> Hi NET-SNMP,
>
> I have recently starting working on SNMP Trapd daemon.
> And I was running a memory leak analysis on the application and came to
> know that there is a leak
> in the below call stack.
> Could someone help me here? Or have I understood it wrong?
>
> LeakTrack+20b07
> msvcr120!malloc+5b
> memdup+53
> netsnmp_set_row_column+138
> log_notification+68b
> notification_handler+8a
> snmp_input+45a
> snmp_vlog+1f2a
> sess_read+b99
> snmp_read+5f
> SnmpTrapdMain+c17
>
>
> Thanks in advance,
> Jeffry Copps, IN
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Net-snmp-coders mailing list
> Net-snmp-coders@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
