Hello kcott,

where are you running your code?

Unfortunately on Perl (v5.14.2) built for MSWin32-x86-multi-thread on win7 and Parallel::ForkManager 1.19 I get more than 50% of crashes, using your code.

Testing more times mine, as posted above, I get ~25% of crashes.. (not saying mine is better: better is no crash at all ;=)

Unfortunately windows is a shaggy beast and I'm not able to debug this behaviour further: what I can add is that during installation I got some warning about disappeared PIDs even if the overall testing process ended ok:

t/00-report-prereqs.t ..... ok
t/01-utf8-all.t ........... skipped: This is a bug in perl itself on W
+indows
t/02-callback.t ........... # This test can take 10-20 seconds, please
+ wait. Started at Thu Sep 21 11:23:08 2017
t/02-callback.t ........... ok
t/03-callback-data.t ...... # This test can take 2-6 seconds, please w
+ait. Started at Thu Sep 21 11:23:25 2017
t/03-callback-data.t ...... ok
t/basic-methods.t ......... ok
t/changing-pids.t ......... ok
t/start_child.t ........... ok
t/waitpid-conflict.t ...... # code outside of P::FM stole -1152
child process '-1152' disappeared. A call to `waitpid` outside of Para
+llel::ForkManager might have reaped it.
t/waitpid-conflict.t ...... ok
t/waitpid-waitonechild.t .. # code outside of P::FM stole -5456
# found warning: child process '-5456' disappeared. A call to `waitpid
+` outside of Parallel::ForkManager might have reap
ed it.
t/waitpid-waitonechild.t .. 1/? # expected to find warning: (?^:child 
+process '\d+' disappeared. A call to `waitpid` out
side of Parallel::ForkManager might have reaped it\.)
t/waitpid-waitonechild.t .. ok
t/waitpid_blocking.t ...... ok
All tests successful.

[download]

L*

PS modified the title a bit for better later search

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

In reply to Re^2: Crash with Parallel::ForkManager on Windows by Discipulus
in thread Crash with ForkManager on Windows by amitsq

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.