I am using strict and warnings, and I get no errors or warnings in the complete code. In terms of isolating the code to find the memory leak.. I have only added the code to the origional question that is causing the mem leak. I need to verify if there is anything funny in that piece of code.

-----
Of all the things I've lost in my life, its my mind I miss the most.

For what it is worth, The full code is on my scratchpad.

-----
Of all the things I've lost in my life, its my mind I miss the most.

In taking a look at your scratchpad, I don't immediately see the cause of your memory leak, but I see something that should help.

At the top of your code, you've predeclared all of your variables. This means that, regardless of where they are used, they exist. For example, you only use $hd_key in your &Setup_Config subroutine. This means that you should only declare it there, and preferably (though some argue this point) you should only declare it right before you use it. This means that all variables should have the smallest possible scope. You have, in effect, used global variables and eliminated part of the benefit of using strict. Consider the following example:

  my $foo;

  sub bar {
    # lots o' code
    $foo++;
    # more code
  }

  sub baz {
    # do a few laps around the pool
    ($foo) = (split)[2];
    # shower and go home
  }
[download]

In the above example, we've reused the variable $foo. For what good? Is it really necessary? This will confuse someone coming to maintain it later. Further, when the subs exit, $foo hangs around when it may not need to. Here's an example of a nice variable declaration:

  sub versive {
    # some pushups
    while ( my ($key,$value)= each %data ) {
      # process things
    }
    #
  }
[download]

In that example, $key and $value exist only in the while loop. This means that the memory they use is available for reuse immediately after the scope of the loop ends (IIRC, the memory is not released back to the OS) and there is no worry about accidentally reusing one of those variables later and possibly having an incorrect value. If you get in the habit of coding like that, your code will be much easier to work with in the long run.

Cheers,
Ovid

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.

I played with this a bit, and it looks like DBD::CSV is what is leaking. The below code leeks ~32K/iteration, and I think the leek is originating from the execute() of a statement that has a WERE clause.

If I drop the size of the where, clause it does not leak as much memory (removing it completely cause nothing to leak), and moving the connect & prepare out of the while(1) loop do not seem to do anything.

What version of SQL Statement do you have? I just tried upgrading to the latest version and that fixed the problem (But the new version is much slower, alas.)

$|++;
use strict;
use DBI;
while(1) {
     my $dbh = DBI->connect("DBI:CSV:f_dir=./")
               or die "Cannot connect: " . $DBI::errstr;
     my $bob = $dbh->prepare("select * from foo where
        1 = 1 OR
        1=1 or 1=2  or 5.6=6 or 7=7 or 9=10 or 11=23 or 6=6 or 7=7 or
        9=10 or 11=23 or 6=6 or 7=7 or 9=10 or 11=23 or 1 = 1 OR
        1=1 or 1=2  or 5.6=6 or 7=7 or 9=10 or 11=23 or 6=6 or 7=7 or
        9=10 or 11=23 or 6=6 or 7=7 or 9=10 or 11=23 or 1 = 1 OR 1=1 o
+r
        1=2  or 5.6=6 or 7=7 or 9=10 or 11=23 or 6=6 or 7=7 or 9=10 or
        11=23 or 6=6 or 7=7 or 9=10 or 11=23 or 1 = 1 OR 1=1 or 1=2  o
+r
        5.6=6 or 7=7 or 9=10 or 11=23 or 6=6 or 7=7 or 9=10 or 11=23 o
+r
        6=6 or 7=7 or 9=10 or 11=23 or 1 = 1 OR 1=1 or 1=2  or 5.6=6 o
+r
        7=7 or 9=10 or 11=23 or 6=6 or 7=7 or 9=10 or 11=23 or 6=6 or
        7=7 or 9=10 or 11=23
     ");
     $bob->execute();
     $bob->finish;
     print ".";
     sleep(1);
}
[download]

sub Check_For_Call
{
    my ($dsm,$server,$agt,$inst_det) = @_;
    my $dbh = ();
    my $sth = ();
    my $query = ();
    $num = ();

    $dbh = DBI->connect(qq{DBI:CSV:f_dir=$xcall_path}) or die &Debug_L
+og("\nDEBUG - Problems Connecting to CSV File\n");
    $dbh->{'csv_tables'}->{'Exist'} = { 'file' => 'ExistCalls',
                    'sep_char' => ';',
                    'eol' => "\n"};

    $query = "SELECT CallNum FROM Exist where Dsm like '$dsm' and Serv
+er like '$server' and Agent like '$agt' and Instance_Detail like '$in
+st_det'";
    #&Debug_Log("SELECT CallNum FROM Exist where Dsm like '$dsm' and S
+erver like '$server' and Agent like '$agt' and Instance_Detail like '
+$inst_det'\n");
        $sth = $dbh->prepare($query) or &Debug_Log("\nDEBUG - Problems
+ Preparing the SQL Statement in Check_for_Call\n");
        $num = $sth->execute() or &Debug_Log("\nDEBUG - Problems Execu
+ting the SQL Statement in Check_for_Call\n");

    if (defined $num) {
        chomp($num);
        $sth->finish();
        $dbh->disconnect();
        return ($num);

    } else {

        #No Call Number Defined
        $sth->finish();
        $dbh->disconnect();
        return (2);
    }

    $sth->finish();
    $dbh->disconnect();
    return(1);
}
[download]

I have moved the declaration of the $dhb variable to the begining of the function where I need it. So it does get re-initialised each time. Still no change to my problem.
-----
Of all the things I've lost in my life, its my mind I miss the most.

require "$mod";
[download]

require "SQL/Dialects/ANSI.pm";
require "SQL/Dialects/AnyData.pm";
require "SQL/Dialects/CSV.pm";
[download]