while(($key, $msg) = each %$msg) {
    process_msg($bs,$msg);
}
[download]

while(($key, $msg) = each %$record)
[download]

You can also make this much easier to read by using a foreach loop (if you only want to handle the msg):

foreach my $msg (values %$records) {
    process_msg($bd, $msg);
}
[download]

Anyway, I wanted to suggest that you look at Perl's profiling package. It can't exactly help you find out where all your memory is going, but it might help you track down where it's being lost. (Note that you should definately be using "my" for each of your variables to ensure that they don't hang around out of scope.)

You can read about Perl's profiling package with perldoc Devel::DProf

The shorts of it are to profile a script run the perl interpreter with the -d switch. So perl -d:DProf test.pl. when it's done, check the results by running dprofpp or dprofpp -T.

I hope that helps. :)

Does the program grow if you leave out that process_msg subroutine call?

Also, use strict and my variables where possible, and don't make circular references like $a = \$b; $b = \$a;, or they'll never really get out of scope (they might go out of scope and be unreachable, but since they refer to eachother, they'll never go away)

Hi,

No, with process_msg the program not gows.

I've investigating more an I detect that the problem could be in the get_msg funtion that looks like:

sub get_msg {


  my $self = shift;


  my ($param) = @_;


  my $consulta_stack = qq{


                         SELECT *


                         FROM out


                         WHERE app = $param


                         ORDER BY id DESC LIMIT 100;


                        };


  my $sth = $self->{dbh}->prepare($consulta_stack);


  $sth->execute();


  my $msgs = $sth->fetchall_hashref('id');


  $sth->finish;


  return $msgs;


}

I also observ that when there's no record in the resultset memory consumption is highter than when there's sontehing.