http://www.perlmonks.org?node_id=873198


in reply to Re: memory not freed after perl exits. Solaris.
in thread memory not freed after perl exits. Solaris.

You can use the "top" command to check for zombies, in case your program is leaving orphaned processes around once it exits - just run it before and after, and see if the zombie count increases.
  • Comment on Re^2: memory not freed after perl exits. Solaris.

Replies are listed 'Best First'.
Re^3: memory not freed after perl exits. Solaris.
by salva (Canon) on Nov 23, 2010 at 12:58 UTC
    zombie processes are reaped by the init process as soon as the main process exits so in practice it is impossible to have orphaned zombie processes!
[reply]
      OK, I probably didn't use the best terminology there. Semantics aside, my point was that the "top" command would allow the user to see if the program was creating zombies in the first place, and hopefully help to debug the issue. Thanks for "clarifying" things and providing valuable pointers.....
[reply]

In Section Seekers of Perl Wisdom