[asterisk-bugs] [Asterisk 0014780]: Asterisk abort (signal 6) in local_pvt_destroy at chan_local.c:159

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14780 
====================================================================== 
Reported By:                jensvb
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14780
Category:                   Channels/chan_local
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-30 01:26 CDT
Last Modified:              2009-04-01 09:38 CDT
====================================================================== 
Summary:                    Asterisk abort (signal 6) in local_pvt_destroy at
chan_local.c:159
Description: 
http://bugs.digium.com/view.php?id=5  0x00002aaab4ff8d08 in local_pvt_destroy
(pvt=0x2aaadc45eff0) at
chan_local.c:159
        __PRETTY_FUNCTION__ = "local_pvt_destroy"

====================================================================== 

---------------------------------------------------------------------- 
 (0102537) jensvb (reporter) - 2009-04-01 09:38
 http://bugs.digium.com/view.php?id=14780#c102537 
---------------------------------------------------------------------- 
>> Are you able to test this on a development system 
>> (which you should be doing whenever you perform an 
>> update -- you shouldn't update production servers 
>> without prior testing)?

Since this is public forum I would like to make the point that we do test
before rolling out. 

It is my opinion that almost everything works in test. The real problems
pop up when you stress test things in the real world.

For the record, we have testing box which we use to test new releases.
Once we feel ok, we move the release to our general office asterisk server.
After about a month, we move the new release to our 100 seat call centre. 
If all goes well..... About 4 times a year (generally) we move that release
to our client call centres.... If all goes well....

>> If file feels some work has already been done here 
>> to solve this, I'm going to be tempted to close this 
>> until you are able to reproduce on a later version 
>> in order to avoid this issue going stale. 

Ok. I will schedule moving 1.4.24 to our general office asterisk server
this Thursday evening. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-01 09:38 jensvb         Note Added: 0102537                          
======================================================================