On 07/05/18 01:21, Ramki wrote: > We are implementing a SNMP agent using the NET SNMP library (C). > As part of the agent we need to handle the trap burst scenario (1250 > traps per second for 75 seconds). We have added a memory based queue > that reads SNMP from the netsnmp_session callback function and > calls snmp_clone_pdu. > We see a very strange behavior. When there are around 100000 traps are > stored after calling snmp_clone_pdu, we see the process memory growth > up to 3 GB. > The memory does not come down even after clearing the traps. > > Can somebody throw light on the net snmp memory handling?
Are you developing for a platform that supports Valgrind? If so, have you tried to analyze the memory leaks with valgrind --leak-check=...? Bart. ------------------------------------------------------------------------------ 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
