[Home]

Summary:ASTERISK-22937: Asterisk crashes with pj_NO_MEMORY_EXCEPTION exception
Reporter:Chetan Goti (chetangoti)Labels:
Date Opened:2013-12-04 06:00:02.000-0600Date Closed:2014-01-21 09:19:05.000-0600
Priority:CriticalRegression?
Status:Closed/CompleteComponents:Resources/res_rtp_asterisk
Versions:11.6.0 Frequency of
Occurrence
Occasional
Related
Issues:
is duplicated byASTERISK-22889 Segmentation fault when RTP going via ICE
Environment:Linux 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/LinuxAttachments:( 0) backtrace_2_Dec.txt
( 1) backtrace_3_dec_1.txt
Description:We are running asterisk in production where the average concurrent calls are ~40 and at peak time, it goes up to ~150+.

We have noticed this attached exception 2 times since the run of 4 days. It seems to be random and we are not able to reproduce it.

We are using icesupport=true for all the sip peers.

I can provide any configuration that might help to debug the issue.

Thanks,
Chetan.
Comments:By: Chetan Goti (chetangoti) 2013-12-04 06:01:38.180-0600

core dump log attached.

By: Matt Jordan (mjordan) 2013-12-07 19:01:32.708-0600

This appears to be similar to or a duplicate of ASTERISK-22889.

Most likely there is either:
# A memory leak that exhausts the resources on the system
# A memory corruption.

Either way, since this issue appears to be happening in pjsip, you can only debug this by running Asterisk under valgrind. Instructions for doing so can be found here: https://wiki.asterisk.org/wiki/display/AST/Valgrind.

Note that this will substantially impact the performance of the system. You will most likely want to attempt this on a lab environment using similar conditions to what you are seeing in production.

By: Chetan Goti (chetangoti) 2013-12-13 05:46:47.954-0600

It does not get replicated in development environment and it will be bad idea to run it under valgrind in production.

Is there anything I can help with?

By: Rusty Newton (rnewton) 2014-01-03 18:39:48.588-0600

Chetan, did you read the section on MALLOC_DEBUG on the https://wiki.asterisk.org/wiki/display/AST/Valgrind page?

Can you try running with that option and provide the mmlog file?

By: Rusty Newton (rnewton) 2014-01-21 09:18:58.808-0600

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines