Yeah, I kind of figured it was an issue with fork being emulated with threads, but I was thrown off and confused by the fact that it worked fine as long as the connections were all concurrent and the fact that the problem didn't arise if sockets weren't involved.

As it turns out, you were correct. The issue was some sort of interaction between sockets and the fork emulation that aggrivated the bug in the regexp engine mentioned explicitly in perldoc perlfork (not sure why I didn't think to check there originally). Upgrading to 5.8.1 fixed it completely (both issues, actually).

Thanks!

bbfu
Black flowers blossom
Fearless on my breath

In reply to Re2: Net::Server::Fork on Win32: Memory access error on pattern match by bbfu
in thread Net::Server::Fork on Win32: Memory access error on pattern match by bbfu

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.