[Ns-bugs] [Bug 134] TCP code leaks memory

[bugzilla-daemon@nsnam-www.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=134


gjcarneiro at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gjcarneiro at gmail.com




------- Comment #2 from gjcarneiro at gmail.com  2008-02-10 07:11 -------
(In reply to comment #0)
> Test case:
> ./waf --run=tcp-small-transfer --command-template="valgrind --tool=memcheck
> --leak-check=full --show-reachable=yes --db-attach=yes %s"
> 
> Some of the leaks seem to be related to sloppy management of new temporary
> PendingData buffers and calls to PendingData::CopyFromSeq.  One possible
> solution is to have this method return a Packet instead of a raw PendingData*.

You could also add reference counting methods to PendingData and then use
Ptr<PendingData> instead of PendingData*.  Just to enumerate all the options,
not saying this one is best...

> 
> Another leak seems to be related to the simulator and scheduling/canceling of
> the retransmission event (possibly related to bug 132?)

class Timer to the rescue! ;-)


-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.