in reply to Re: Suppressing thread warnings
in thread Suppressing thread warnings

This did the job! Can you please explain what this actually does? I want to make sure it doesn't negatively affect my app. Note that it exists at the end of each run, so I'm not worried about garbage collection over a long period.

Replies are listed 'Best First'.
Re^3: Suppressing thread warnings
by BrowserUk (Patriarch) on Oct 10, 2008 at 21:16 UTC

    POSIX::_exit() calls your C-runtime to terminate the process. That bypasses all Perl contructs including END{} blocks and DESTROY() subroutines. Effectively, it completely bypasses Per's usual clean-up routines.

    In doing so, it bypasses the perl-core code that detects that there are still threads running and produces the warning. But, it can also give problems if you are using modules that use DESTROY subs or END blocks to persist data, flush buffers and the like.

    You can often cause object DESTROY methods to be called by undefing the handles, but I don't know of any way of forcing END blocks to be run without going through the full perl clean-up process.

    In other words, use _exit() with caution.


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.