[asterisk-bugs] [Asterisk 0013703]: Abort in free in queue show <name> command

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13703 
====================================================================== 
Reported By:                davidw
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   13703
Category:                   Applications/app_queue
Reproducibility:            have not tried
Severity:                   crash
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.0 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-15 08:56 CDT
Last Modified:              2008-10-15 11:47 CDT
====================================================================== 
Summary:                    Abort in free in queue show <name> command
Description: 
We were getting bogus queue not found messages from the QUEUE_MEMBER (and
QUEUE_MEMBER_COUNT function), so after running "queue show", which gave the
truncated queue name, we tried queue show <name> with the full name.
====================================================================== 

---------------------------------------------------------------------- 
 (0093730) davidw (reporter) - 2008-10-15 11:47
 http://bugs.digium.com/view.php?id=13703#c93730 
---------------------------------------------------------------------- 
WRT to the two different issues.  I was going to report the queue function
not finding the queue one separately, when I'd investigated a bit more, but
mentioned it here as it was in that context that I generated the crash; I
was trying to see if the name had been physically truncated.

It may, of course, be that the memory corruption led to the failure to
find.  However, I think there has to be more to it, otherwise I presume it
would have been found before.

As to the reference counts, note that they are going distinctly negative. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-15 11:47 davidw         Note Added: 0093730                          
======================================================================