[Click] No cleanup?

[Michael Neufeld]

It's been a while, but as I recall that's likely the result of some 
laziness on my part a couple of years ago. Since the simulated world and 
its associated process is destroyed when ns-2 finishes, the operating 
system reclaims its memory, and I seem to remember not bothering to 
explicitly destroy the Click instance on the way out. It's probably on 
an old "nsclick todo" list somewhere... If it's causing problems, i.e. 
you're allocating something which doesn't get cleaned up by the OS on 
exit or it's masking a memory leak you're trying to track down, you 
should be able to explicitly destroy the router on exit and do more 
thorough cleanup.

-Mike

Bart Braem wrote:
> Hello,
> 
> I'm doing some memory checks and a lot of elements don't seem to free their 
> memory at the end which is very strange. After some investigation I 
> discovered cleanup isn't called, in fact the destructor of Router is never 
> called. Is that normal? I'm using nsclick so should I look there?
> 
> Bart
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click