Version: net-snmp-5.5
I think the 5.5.x version does support the -X argument.
Let me try running the test on 5.7.3 and check if the same leak is detected
again.
If there is a root cause found for 5.5 version, that would be great.
Updating to 5.7.3 is complex as many other applications are using the same
project.
Thanks,
Jeffry copps
jeffry
On Sat, Jul 29, 2017 at 7:03 PM, Bill Fenner <fen...@gmail.com> wrote:
> What version of net-snmp are you using? I looked at the code in 5.7.3 and
> don't see how that leak could happen.
>
> If your version of snmptrapd accepts the -X argument, try passing that to
> avoid calling this code path altogether.
>
> You could help debug futher by passing "-Dnetsnmp_sockaddr_in" and see
> what messages you get; that should point to what code path to investigate
> further.
>
> Bill
>
>
> On Tue, Jul 25, 2017 at 1:36 AM, Jeffry Copps <jeffrycopps1...@gmail.com>
> wrote:
>
>> Fenner,
>>
>> I tried adding the doNotRetainNotificationLogs=yes.
>> The following is what I got from DebugDiag, Could you help me here.
>>
>> Function details
>>
>> Function msvcr120!malloc+5b
>> Source Line
>> Allocation type Heap allocation(s)
>> Heap handle 0x00000000`00000000
>> Allocation Count 130354 allocation(s)
>> Allocation Size 11.58 MBytes
>> Leak Probability 95%
>>
>>
>> Call stack sample 1
>>
>> Address 0x00326300`35303700
>> Allocation Time 04:15:14 since tracking started
>> Allocation Size 5 Bytes
>>
>>
>> Function
>>
>> Destination
>>
>> LeakTrack+20b07
>> msvcr120!malloc+5b
>> msvcr120!_strdup+28
>> netsnmp_sockaddr_in2+150
>> netsnmp_sockaddr_in2+134
>> netsnmp_tcp_create_tstring+24
>> netsnmp_tdomain_transport_full+508
>> netsnmp_transport_open_client+18
>> subagent_open_master_session+125
>> agentx_reopen_session+82
>> run_alarms+ce
>> SnmpTrapdMain+c28
>>
>>
>> Thanks,
>> Jeffry copps
>>
>>
>>
>> jeffry
>>
>> On Thu, Jul 13, 2017 at 2:47 PM, Bill Fenner <fen...@gmail.com> wrote:
>>
>>> 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
