[Home]

Summary:ASTERISK-11944: Segmentation Fault in autoservice_run
Reporter:Arnd Schmitter (arnd)Labels:
Date Opened:2008-04-30 03:27:18Date Closed:2011-06-07 14:00:51
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) bt.txt
Description:Our Asterisk crashed with a segmentation fault.
With gdb i've created a backtrace of the crashed thread (see files).
The channel involved was waiting inside a queue and listening to the musiconhold.
I can't say for sure, if the channel was already waiting or just started to wait (hear musiconhold).
Comments:By: Mark Michelson (mmichelson) 2008-05-02 16:41:37

I would like to know if this issue still occurs in 1.4.20-rc1. The reason is that since the creation of the 1.4.18 tag, there have been some massive bug fixes in autoservice, and so the problem you experienced might be resolved.

By: Arnd Schmitter (arnd) 2008-05-13 07:28:36

Hi putnopvut.

We can't use 1.4.19/1.4.20-rc1. These Versions doesn't run stable and crashes after a few Minutes.

Under 1.4.18 it doesn't happen again until now.
If the crash repeats someday, i will post a new comment.

By: Mark Michelson (mmichelson) 2008-05-14 17:33:42

Crashes after a few minutes? That's pretty terrible. Have you reported the crashes that have occurred? If not, do you know if any of the other open bugs correspond to the crashes you're experiencing on the newer versions?

By: Arnd Schmitter (arnd) 2008-05-15 01:56:48

There are already Bugreports matching our Problems with 1.4.19/1.4.20-rc1.
The crashes were related to Chanspy.

By: Joshua C. Colp (jcolp) 2008-06-10 09:23:01

So where do we stand with this?

By: Arnd Schmitter (arnd) 2008-06-12 02:02:56

Until now, it doesn't had happen again.
You can close the Report and if it happens again, i will reopen it.

By: Joshua C. Colp (jcolp) 2008-06-16 07:20:41

Suspended per reporter.