in reply to Re^2: Child process lingers after keyboard interrupt on Windows
in thread Child process lingers after keyboard interrupt on Windows

So trying to fork() I run into the this issue:

When the pseudo-child process (really a new thread in the parent, see perl fork() emulation for Windows) reopens STDOUT, the parent STDOUT changes as well. Although perl documentation says the open handles are duplicated on emulated fork(), to prevent this issue.
  • Comment on Re^3: Child process lingers after keyboard interrupt on Windows

In Section Seekers of Perl Wisdom