Hey all,

I have a piece of code here that uses Thread::Queue. I wrote it as a test case when I was rooting around with Devel::Leak. This sucker will eat every ounce of memory I have and then my lunch if I let it. Can anyone tell me why? For some reason, it seems like dequeue does not free up the memory when it dequeues. Should I be using a different module?

smiles 

#!/usr/bin/perl

use strict;
use threads;
use Thread::Queue;

my $q = Thread::Queue->new();
for (1..3) {
    $q->enqueue('A' x 100);
    threads->new(\&ttest)
}
my @threadlist = threads->list;
sleep 100;
$q->enqueue(undef) for @threadlist;
$_->join for @threadlist;

sub ttest {
    while (my $item = $q->dequeue) {
        my $cnt = $q->pending;
        print "$cnt\n";
        $q->enqueue('A' x 100);
    }
}

[download]

In reply to Thread::Queue and Memory by petesmiley

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.