I think we have already concluded that the non-balanced BEGIN/END printouts can be explained by the process being interrupted by a signal before it reaches the code or the buffer is flushed. ... see straces above
What puzzles me is that this all causes Perl to redo the entire destruction of the perl object - passing DESTROY a new reference to the same object.
It might be that the shutdown of the one process causes an interrupt in the other process due to their IPC (preforking uses an IPC mechanism for managing workers). I've seen this happen hundred of times now, sometimes in the parent, sometimes in a child... but only ever in 1 process out of N workers + a parent.
So there might be a Net::Server bug causing unorderly shutdown of the processes... but anyway... That should result in DESTROY methods not being called. Not that Perl calls the DESTROY method twice in the same process
In reply to Re^4: Is this absurd, or have I not RTFM?
by petermogensen
in thread Is this absurd, or have I not RTFM?
by petermogensen
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |