[asterisk-bugs] [Asterisk 0018950]: [patch] Deadlock: ast_taskprocessor_get and SIP
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Mar 28 08:00:41 CDT 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18950
======================================================================
Reported By: alecdavis
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18950
Category: Core/General
Reproducibility: unable to reproduce
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.8.2.3
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-03-09 15:09 CST
Last Modified: 2011-03-28 08:00 CDT
======================================================================
Summary: [patch] Deadlock: ast_taskprocessor_get and SIP
Description:
Has only locked up once, but have been running 1.8.2.3 for a few weeks now,
and are unable to reproduce at this stage.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0018310 [patch] hint state changes deadlock/race
======================================================================
----------------------------------------------------------------------
(0133136) one47 (reporter) - 2011-03-28 08:00
https://issues.asterisk.org/view.php?id=18950#c133136
----------------------------------------------------------------------
Irontec, the information in https://issues.asterisk.org/view.php?id=18629 only
applies after the patch in https://issues.asterisk.org/view.php?id=18310
has been applied as https://issues.asterisk.org/view.php?id=18310 causes a
change in how the locks are used.
Under load, we could cause locks in a few hours without
https://issues.asterisk.org/view.php?id=18310. We've had
one lockup since, over a period of a couple of months, and I believe that
https://issues.asterisk.org/view.php?id=18629 might be the reason for it.
Issue History
Date Modified Username Field Change
======================================================================
2011-03-28 08:00 one47 Note Added: 0133136
======================================================================
More information about the asterisk-bugs
mailing list