Bug #9837 for DBD-SQLite: Memory Leak

Mon Jan 17 17:37:17 2005 Guest - Ticket created

Subject:

Memory Leak

I did some testing that simply put database connection and disconnection in a loop and I watched the resident memory requirement of the program increase. Given that it was a DBD driver, I decided it was too complicated to debug. I saw, for example, that error messages are freed when they need to be, etc... So I wrote my own code that didn't rely on DBD. I put this bug on the list in the hope that the memory issues are resolved. Now that I wrote my own, I understand how to debug memory leaks in PERL XS modules so, if I have time, I'll look into this issue deeper.

Fri Oct 21 08:42:45 2005 Guest - Correspondence added

I just wanted to add to this report that I found the same problem in 1.09. I've reproduced the leak under ActiveState 5.8.3 with the following code... use strict; use DBI; while(1) { my $dbh = DBI->connect("dbi:SQLite:test.db") or die "Unable to connect\n"; $dbh->disconnect() or die "Unable to disconnect\n"; }

Wed Dec 07 08:48:01 2005 Guest - Correspondence added

From:

mrdamnfrenchy [...] yahoo.com

Still leaky in 1.11.

Thu Apr 13 15:07:43 2006 Guest - Correspondence added

From:

mrdamnfrenchy [...] yahoo.com

Still leaky in 1.12.

Thu Apr 13 15:07:44 2006 The RT System itself - Status changed from 'new' to 'open'

Thu Sep 07 23:33:25 2006 msergeant [...] cpan.org - Correspondence added

Can't replicate with new cvs code. Re-open if this is still an issue after 1.13.

Thu Sep 07 23:33:26 2006 msergeant [...] cpan.org - Status changed from 'open' to 'resolved'