Seems, that the current setup is too big/expensive to be handled by your machine?
I would check the value of @ciaona_pwm_array first. Is it too big or other than expected?
$seq_1 and $seq_2 seems to stay constant. Are you sure, you're partition the task correctly? I.e., due to the fork() if you change some global variables, the change will only take place in the copy of the process (child) and not back-communicated to the parent who should perform the partition task (ok, that's speculation, but perhaps it triggers an idea...?).
Perhaps, you can reduce the memory footprint of the parent before the fork takes place, e.g. let the child read only a chunk of data to be processed?

In reply to Re: Cannot fork in Parallel::ForkManager by Perlbotics
in thread Cannot fork in Parallel::ForkManager by plagent

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.