Re^4: Memory consumption of forks on exit

Yeah, right! Didn't think of that. Could be a solution, but it's still not really pretty, because that exits are scattered all over the place (not my fault).

/me dances around a bit as it was suggested

Comment on Re^4: Memory consumption of forks on exit

Replies are listed 'Best First'.
Re^5: Memory consumption of forks on exit by salva (Canon) on May 19, 2011 at 11:55 UTC
I seems I have not explained clearly my workaround. Let my try again with some sample code: `END { # sub END { OOPS!!! do_something(); POSIX::_exit(0); } do_this(); do_that(); exit(0);` [download] update: `sub` in front of `END` removed!	[reply] [d/l] [select]
Re^6: Memory consumption of forks on exit by egga (Monk) on May 19, 2011 at 12:04 UTC
I'm sorry, but that doesn't work out on my machine. The peak is still there	[reply]
Re^7: Memory consumption of forks on exit by Marshall (Canon) on May 19, 2011 at 13:12 UTC
An END block is not a sub. Take sub off. Just END{...}. The END block will execute before program really exits thereby calling the type of exit you want instead of the normal one as previous monk pointed out.	[reply]
Re^8: Memory consumption of forks on exit by chromatic (Archbishop) on May 19, 2011 at 16:47 UTC
Re^8: Memory consumption of forks on exit by ikegami (Patriarch) on May 19, 2011 at 21:28 UTC
Re^8: Memory consumption of forks on exit by egga (Monk) on May 19, 2011 at 13:49 UTC
Re^9: Memory consumption of forks on exit by Marshall (Canon) on May 19, 2011 at 14:22 UTC
Some notes below your chosen depth have not been shown here