Summary: | ASTERISK-16647: Asterisk Crashes after 70 calls | ||
Reporter: | Alberto Fernandez Crespo (afernandez235) | Labels: | |
Date Opened: | 2010-09-03 15:05:41 | Date Closed: | 2011-06-07 14:00:27 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | After over 70 calls asterisk crashes. Here is the backtrace. Inline trace removed - pabelanger ---- Server information Quad Core Intel(R) Xeon(TM) CPU 3.00GHz Linux 2.6.18-194.8.1.el5PAE #1 SMP Thu Jul 1 19:46:23 EDT 2010 i686 i686 i386 GNU/Linux Im running Asterisk ver 1.6.2.2 (Its not an option on the Drop down menu) | ||
Comments: | By: Paul Belanger (pabelanger) 2010-09-04 14:02:18 Please upload an unoptimized backtrace (see below). --- Thank you for your bug report. In order to move your issue forward, we require a backtrace from the core file produced after the crash. Please see the doc/backtrace.txt file in your Asterisk source directory. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then: make install after enabling, reproduce the crash, and then execute the instructions in doc/backtrace.txt. When complete, attach that file to this issue report. Thanks! By: Leif Madsen (lmadsen) 2010-09-07 12:50:20 Backtrace attached to the issue is required to move this forward. By: Paul Belanger (pabelanger) 2010-11-24 08:54:13.000-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 |