> this doesn't apply to my needs, but are DB connects cached as well
> with a separate 120 counter?
I'm sort of out of my league here, but I think DBI caches the db handles as
well as statement handles, and all of them are cleared every 120. So even
though you are undef'ing them, they are cache
On Aug 23, 2006, at 8:55 AM, Ephraim Dan wrote:
I tried to reproduce your leak without success. Perhaps you are
not letting your test run for enough iterations. DBI does cache
some handles that it only releases every 120 calls. So you could
see what looks like a 1 SV leak, but you'll se
On Aug 23, 2006, at 8:55 AM, Ephraim Dan wrote:
I hope Tim will chime in and correct me, but since I was the last
reporter of leaks in the DBI, let me try my best:
great i'll try all that stuff than let you know
/]}
);
$sth->execute();
while ( my ($a,$b) = $sth->fetchrow_array() ) {
print "a:$a,b:$b\n";
}
$sth->finish;
$dbh->disconnect;
> -Original Message-
> From: Jonathan [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 23, 2006 04:52
> To: dbi-users@perl.org
&
it definitely seems to be a leak, and i've been able to reproduce it
outside of mod_perl
it seems that there are a few potential sources / behaviors
a_ the statement handle created by a prepare never seems to expire
in the lifetime of a db connection
i could trace this a
Hi.
I'm running 1.52 and I may have found a leak ( i found a discussion
reported on the 1.51 branch, and a patch to 1.52, so i think this
might be different )
I was profiling some mod_perl code for unexplained growth with
Devel::Leak, and came across a growth of 1 reference count with ev
