[asterisk-bugs] [Asterisk 0016974]: Deadlocks with ~2k MGCP users
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Mar 8 10:10:29 CST 2010
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=16974
======================================================================
Reported By: adrien
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16974
Category: Channels/General
Reproducibility: unable to reproduce
Severity: major
Priority: normal
Status: feedback
Asterisk Version: 1.4.29.1
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-03-05 14:30 CST
Last Modified: 2010-03-08 10:10 CST
======================================================================
Summary: Deadlocks with ~2k MGCP users
Description:
I experience a freeze of Asterisk when I was in 1.2.35 due to 'Avoided
deadlocks'.
So I move to 1.4.29.1 release and the issue seems to be the same. One
difference : I don't have "Avoided deadlocks" into Warning level but only a
lot of "Avoiding" during the day and ONE (ie. On one channel) repeated
several times after Asterisk has freezed.
I can post some debug output but not backtrace yet because I must
recompile with DEBUG_THREADS = #-DDUMP_SCHEDULER #-DDEBUG_SCHEDULER
#-DDEBUG_THREADS #-DDETECT_DEADLOCKS
======================================================================
----------------------------------------------------------------------
(0119107) lmadsen (administrator) - 2010-03-08 10:10
https://issues.asterisk.org/view.php?id=16974#c119107
----------------------------------------------------------------------
Thanks for the submission! I'm putting this into feedback until you can
provide some additional information (such as the backtrace you appear to be
working on getting, etc...).
It may or may not also be useful to get some valgrind output, but since
that will slow your system down significantly then I think the backtrace
and 'core show locks' output will be the best usage of time right now.
Issue History
Date Modified Username Field Change
======================================================================
2010-03-08 10:10 lmadsen Note Added: 0119107
2010-03-08 10:10 lmadsen Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list