Re: Memory consumption of forks on exit

That happens because when the interpreter shuts down, it deallocates all the Perl structures one by one, effectively writing to the memory where they are stored.

Under Unix/Linux, that means that as the memory is write-accessed, the kernel has to perform a copy-on-write of the underlaying pages.

As a workaround, try calling _exit or exec "/bin/true"; at the end of the END blocks.

Comment on Re: Memory consumption of forks on exit Select or Download Code

Replies are listed 'Best First'.
Re^2: Memory consumption of forks on exit by egga (Monk) on May 19, 2011 at 11:22 UTC
Ok, thats a good explanation. But I still want to execute the end blocks of the children, which doesn't happen if I try your workarounds.	[reply]
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
Re^6: Memory consumption of forks on exit by egga (Monk) on May 19, 2011 at 12:04 UTC
Some notes below your chosen depth have not been shown here