Bug 1173 – Valgrind detects memory leaks from Click when using ns-3-click

Bug 1173 - Valgrind detects memory leaks from Click when using ns-3-click


Summary:	Valgrind detects memory leaks from Click when using ns-3-click

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	click
Version:	pre-release
Hardware:	All All

Importance:	P5 normal
Assigned To:	Ruben Merz

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-05-26 15:32 EDT by Lalith Suresh
Modified:	2012-02-19 10:34 EST (History)
CC List:	2 users (show)

See Also:

Attachments
Ipv4ClickRouting patch (926 bytes, patch) 2011-05-26 15:32 EDT, Lalith Suresh	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Lalith Suresh 2011-05-26 15:32:39 EDT

Created attachment 1149 [details]
Ipv4ClickRouting patch

Seems like valgrind is complaining about the memory that Click allocates for its elements and other components which are not essentially meant to be deallocated by Click (i.e, they're cleaned up automatically by the OS when the click process terminates). This can be seen by running:

$: ./waf --run nsclick-simple-lan --command-template="valgrind --leak-check=full --show-reachable=yes %s"

I've attached a patch to Ipv4ClickRouting which helps get rid of a few of the complaints.

Comment 1 Lalith Suresh 2012-01-20 11:18:55 EST

Partially fixed in changesets 7691:63e7bd888869 and 7690:6079432abbae.

Comment 2 Lalith Suresh 2012-02-19 10:34:53 EST

Seems like the rest of the leaks originate from within Click and is confusing valgrind, so I'm closing this now.