| Summary: | ASTERISK-15995: Asterisk crashes sometimes (device state?) | ||
| Reporter: | robert Frerichs (robtor) | Labels: | |
| Date Opened: | 2010-04-21 15:22:43 | Date Closed: | 2011-06-07 14:00:39 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | PBX/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) backtrace_2010_05_04.txt ( 1) backtrace.txt ( 2) backtrace-threads.txt | |
| Description: | i have made an gdb dump <inline backtrace removed> | ||
| Comments: | By: Paul Belanger (pabelanger) 2010-04-21 15:30:56 Your report lacks information about your issue. What was Asterisk doing when it crashed? Can you reproduce it? ETC. The more information better. Also, please don't post your backtrace as a comment, upload as a file. It will also help to generate a full backtrace too. http://svn.asterisk.org/svn/asterisk/trunk/doc/backtrace.txt --- Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. You may find it helpful to read the Asterisk Issue Guidelines http://www.asterisk.org/developers/bug-guidelines. We\'d be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). This likely includes output from the console with debug level logging, a SIP trace (if this is SIP related), and configuration information such as dialplan (e.g. extensions.conf) and channel configuration (e.g. sip.conf). Thanks! By: Leif Madsen (lmadsen) 2010-04-21 15:41:57 Is this being generated like instructed in http://svn.asterisk.org/svn/asterisk/trunk/doc/backtrace.txt ? It looks like you're missing some data here. Also have you enabled DONT_OPTIMIZE in the Compiler Flags of menuselect? By: robert Frerichs (robtor) 2010-04-21 15:43:17 no, i dont Can reproduce it! my asteriskversion is 1.4.4 and has 263 hints, with 250 extension. i pute my backtrace in a file and send it tomorrow! By: robert Frerichs (robtor) 2010-04-22 02:00:22 so, i have upload the files and i hope it`s right! thank you for help! By: Leif Madsen (lmadsen) 2010-04-22 09:31:46 The backtraces are fine -- I deleted the core-show-locks.txt file because it was useless. It showed up as Chinese (or some other pictoral language) for me. By: robert Frerichs (robtor) 2010-04-23 06:52:13 1. Register 1...250 SIP-devices as users with subsequent SUBSCRIBEs, hints enabled. 2. Asterisk segfaults with coredump intermittently. By: Andrew Latham (lathama) 2010-04-23 08:46:32 Related issue. We had the Asterisk process crash during mass updates in the GUI. Last example was adding voicemail to 391 users at once. By: Leif Madsen (lmadsen) 2010-04-26 14:17:58 This is definitely going to be a tough issue to reproduce in the lab because my desktop is not big enough for 250 phones ;) By: Ulf Theobald (tweety) 2010-04-29 19:46:40 I've also taken a closer look at the source. I think it's pretty weird to check if tmp is a NULL pointer after accessing it, by using strcmp. Why could tmp->name be a NULL pointer or something similar? By: robert Frerichs (robtor) 2010-05-04 07:43:41 i have upload a backtrace from a chrash at the 2010-05-04! By: Leif Madsen (lmadsen) 2010-05-04 15:30:27 robtor: your backtrace contains several lines with <value optimized out> Have you followed the instructions at http://svn.asterisk.org/svn/asterisk/trunk/doc/backtrace.txt ? By: Tilghman Lesher (tilghman) 2010-05-26 22:16:51 Additionally, you've set the version field to 1.4.30, but you've stated that your version is 1.4.4. Which version are you actually running? By: Paul Belanger (pabelanger) 2010-06-18 10:03:14 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 | ||