[asterisk-bugs] [JIRA] (ASTERISK-24152) memory leak and segfault with in libpthread-2.17.so

[Walter Doekes (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-24152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222816#comment-222816 ] 

Walter Doekes commented on ASTERISK-24152:
------------------------------------------

What does 'sip show objects' and 'sip show registry' say (after a couple of hours)?

I'm tempted to blame callbackexten, since that's relatively new in conjunction with realtime.



> memory leak and segfault with in libpthread-2.17.so
> ---------------------------------------------------
>
>                 Key: ASTERISK-24152
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24152
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General, Resources/res_pjsip
>    Affects Versions: 12.4.0
>         Environment: 12.4.0 
> Ubuntu 13.10
>            Reporter: Yuriy Gorlichenko
>            Assignee: Rusty Newton
>         Attachments: backtrace_bt_full.txt, backtrace.txt, memsummary_hour.txt, memsummary_start.txt, mmlog, valgrind.txt
>
>
> Hello. I have issue with asterisk 12.4.0 with memory leak.
> I have installed asterisk 12.4.0 at Ubuntu 13.10 with realtime chan_sip and pjsip modules (at diffrent ports: chan_sip used as trunk channel and pjsip runs as client side).
> I see at syslog that my system fails futh segfault:
> kernel: [17857.689103] asterisk[23250]: segfault at 2cf ip 00007ff84a294164 sp 00007ff79aeb75a0 error 4 in libpthread-2.17.so[7ff84a28b000+17000]
> Then i open "top" appliation and monitor memory that used by asterisk. I monitored it at 1.5 hour and all this time memory usage grows (number of calls at one time always 2-5). So at start I see 3,3% of usage and then after 1.3 hour I see 11,5% usage.
> I recompiled my asterisk with MALLOC_DEBUG and use from asterisk CLI "memory show summary" at start and after hour of work.



--
This message was sent by Atlassian JIRA
(v6.2#6252)