You don't show much relevant code, and you don't tell us much about the environment you're working with, so I'm going to make some assumptions:

This is problematic as the threads will see the references pointing to the same thing and then stomp on each others values.

You could have shown the relevant code of the "subroutine that makes $accptr vanish", but you chose not to. Perl has reference counting and no garbage collection, so things don't simply vanish. You have a logic error somewhere.

As a remedy, I would look into using a Thread::Queue to hand off jobs to worker threads. This will force you to avoid global variables for passing information and it will properly clone information across threads so they don't step on each others toes.


In reply to Re: Postpone garbage collection during a child process run? by Corion
in thread Postpone garbage collection during a child process run? by flexvault

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.