An update to my last post. The pure perl script isnot quite correct. Should have called a sub to read the file like this: 
#!/usr/bin/perl
use warnings;
use strict;

my $in_file="\\in_dile\.txt";
my $count_runs=0;


while (1) {
    $count_runs++;
    read_file();
    print "run $count_runs\n";
    <>;
}

sub read_file {
    my @data;
    open MYFILE ,$in_file or die "Could not open file to read:$in_file
+\n";
    while(<MYFILE>) {
        my $temp=$_;
        chomp $temp;
        my @array=split("\t",$temp);
        push(@data,[@array]);
    }
    close MYFILE;
}

[download]

An like in the Perl/TK app, the memory leak is there. Maybe I am doing something wrong with the anonymous array. But again, should the local vars be cleared when going out of scope in every call to the sub.

In reply to Re: TK::ProgressBar and update memory build up by saskak
in thread TK::ProgressBar and update memory build up by saskak

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.