in reply to POE::Wheel::Run & MSWin32 problem

Have you tried POE::Wheel::Run::Win32? It may be that the exit() in POE::Wheel::Run is exiting the entire program, since fork() is being emulated by threads there.

Replies are listed 'Best First'.
Re^2: POE::Wheel::Run & MSWin32 problem
by cmv (Chaplain) on Aug 11, 2009 at 18:59 UTC
    Using POE::Wheel::Run::Win32 seems to cause various errors to occur, but the most prominent is:

    ERR: Free to wrong pool 3558130 not 235f40 at c:/Perl/lib/Tk/After.pm line 86.

    Update: rcaputo++
    I have opened a ticket as you have asked. Many thanks!

      This sounds like a bug in POE::Wheel::Run and/or POE::Wheel::Run::Win32, which isn't surprising as I haven't had access to a good Win32 machine until recently.

      It could also be a problem with Tk and forking, which is really threading in Windows. Tk may be shutting down when one thread stops. To Tk it may look as if the program is done. I'm not sure, but I'll have some time to find out soon.

      Please open a ticket at POE's queue at rt.cpan.org, and attach your test program. It will help me track and prioritize this issue. I'll also ping Chris Williams (the author of POE::Wheel::Run::Win32) on IRC to see if he knows something about it.

      Thank you.