[asterisk-bugs] [Asterisk 0014974]: [patch] erros messages astobj2.c INTERNAL_OBJ

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14974 
====================================================================== 
Reported By:                pj
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   14974
Category:                   Core/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 190545 
Request Review:              
====================================================================== 
Date Submitted:             2009-04-27 03:22 CDT
Last Modified:              2009-05-12 07:28 CDT
====================================================================== 
Summary:                    [patch] erros messages astobj2.c INTERNAL_OBJ
Description: 
after updating from Asterisk SVN-trunk-r183057 to Asterisk
SVN-trunk-r190545
a lot of errors like below appears on console during asterisk startup and
when sip peer registers (subscribe to hins)
it seems, that this issue doesn't affect normal asterisk operation.
====================================================================== 

---------------------------------------------------------------------- 
 (0104573) dhubbard (reporter) - 2009-05-12 07:28
 http://bugs.digium.com/view.php?id=14974#c104573 
---------------------------------------------------------------------- 
In my opinion, this issue should be upgraded from a 'minor' severity to
'crash' or at least 'major'.

You can crash Asterisk by simply connecting and disconnecting a manager
session.

Matt Nicholson confirmed to me over IRC that he also reproduced the crash
by connecting and disconnecting a manager session.  You don't have to do
anything in the manager session to reproduce this crash. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-12 07:28 dhubbard       Note Added: 0104573                          
======================================================================