I replaced the threads->exit() with a return(0); and the crashes are still occurring the same way. From my understanding threads->exit() functioned the same as return(undef).
As far as the use of the cond_* functions, they are used internally in Thread::Queue, which was in use in the other thread you pointed towards.
I'm trying to work backwards from the apparent win32 VMem corruption resulting in the "free to wrong pool", to see what might have overrun some memory.
I'm usually a Unix programmer, so debugging under Windows is a bit out of my comfort zone.
Let me know if there are other things to try.

In reply to Re^2: Having Win32 Perl crashs using ithreads by dchidelf
in thread Having Win32 Perl crashs using ithreads by dchidelf

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.