Re^2: Memory consumption of forks on exit

Replies are listed 'Best First'.
Re^3: Memory consumption of forks on exit by Anonymous Monk on May 19, 2011 at 11:36 UTC
Then its simple, don't use end blocks, instead use `used_to_be_an_end_block(); dance(); POSIX::_exit(0);` [download]	[reply] [d/l]
Re^4: Memory consumption of forks on exit by egga (Monk) on May 19, 2011 at 11:45 UTC
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	[reply]
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
Re^7: Memory consumption of forks on exit by Marshall (Canon) on May 19, 2011 at 13:12 UTC
Some notes below your chosen depth have not been shown here