[asterisk-bugs] [Asterisk 0018098]: Many "rtp.c: RTP Read too short" errors followed by memory exhaustions and crash

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18098 
====================================================================== 
Reported By:                mhampton
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18098
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.14-rc1 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-10-05 18:48 CDT
Last Modified:              2010-10-06 13:21 CDT
====================================================================== 
Summary:                    Many "rtp.c: RTP Read too short" errors followed by
memory exhaustions and crash
Description: 
Occasionally a channel will get numerous rtp.c: RTP Read too short errors
with seemingly random numbers.  When this happens, I often get a memory
exhaustion error followed by a crash.  This has been happening in both
1.6.2.13 and 1.6.2.14-rc1.  It has happened several times over the past
week.
====================================================================== 

---------------------------------------------------------------------- 
 (0127762) schmidts (manager) - 2010-10-06 13:21
 https://issues.asterisk.org/view.php?id=18098#c127762 
---------------------------------------------------------------------- 
Could you please add the backtrace if you have a core dump and also debug
logs if this is easy to reproduce for you.

have a look at the doc/backtrace.txt file to see how to generate a
backtrace we need and dont forget to set the DONT OPTIMIZE Flag and
recompile asterisk before creating the backtrace.

thank you 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-06 13:21 schmidts       Note Added: 0127762                          
======================================================================