[asterisk-bugs] [Asterisk 0013331]: [patch] chan_sip is leaking in build_peer
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Oct 23 07:03:49 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13331
======================================================================
Reported By: sergee
Assigned To: russell
======================================================================
Project: Asterisk
Issue ID: 13331
Category: Channels/chan_sip/General
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0
SVN Revision (number only!): 138147
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-08-18 03:26 CDT
Last Modified: 2008-10-23 07:03 CDT
======================================================================
Summary: [patch] chan_sip is leaking in build_peer
Description:
I'm using RealTime setup with 1.6.0 branch. Asterisk runs out of memory in
a 2 days.
======================================================================
----------------------------------------------------------------------
(0094198) russell (administrator) - 2008-10-23 07:03
http://bugs.digium.com/view.php?id=13331#c94198
----------------------------------------------------------------------
The trunk patch isn't quite right. When this object was converted to
astobj2, removing the ast_free() from there was the right thing to do. In
astobj2, the object itself gets free'd for you. The destructor only cleans
up internal allocations. With astobj (which is what is used in 1.6.0), the
destructor has to free the object itself, as well.
I'll work on integrating your 1.6.0 patch today.
Thanks!
Issue History
Date Modified Username Field Change
======================================================================
2008-10-23 07:03 russell Note Added: 0094198
======================================================================
More information about the asterisk-bugs
mailing list