Re: [Sqlgrey-users] Memoryleak in sqlgrey 1.6.7

[Lionel B. <lio...@bo...>]

Casey Feskens wrote the following on 11.09.2006 20:30 :
> We've been testing an implementation of sqlgrey 1.6.7 and have
> come across a memory leak fairly rapidly.  Under our current
> load (30,000 msgs/day, 6000 users), sqlgrey's heap seems to be
> growing by about 1MB every 5 minutes.
>
> Another copy of sqlgrey not actively in use does not seem to be
> gaining any memory, so it looks like this issue only occurs when
> the daemon is in active use.
>
> I noticed a previous thread on this list about memory leaks in
> 1.6.7, but no resolution.  Has anyone else seen this:
>
> Our configuration:
>
> Solaris 9
> Postfix 2.2.10
> Perl 5.8.4
> Sqlgrey 1.6.7
>
> Thanks for any help you may be able to provide.
>
>   

I recently had an unrelated problem with DBD-Pg and investigated the 
"Changes" files of DBI (Perl's database API) and DBD-Pg (Perl DBI's 
PostgreSQL driver) by downloading the latest versions available from 
CPAN. I've spotted reports of memory leaks fixed in DBI 1.52 (latest 
available) and DBD-Pg 1.44 (current is 1.49, which, for me, solved a 
prepared statement problem when DBD-Pg was compiled with GCC 4.1.1). You 
should check your DBI version and if you use PostgreSQL, please check 
DBD-Pg's version too.

That said, given the simple algorithms used it's highly unlikely that 
SQLgrey would suffer from memory leaks (you have to do pretty fancy 
stuff to make Perl lost track of the memory it should free). I believe 
most of the currently reported problems with 1.6.x are either bugs in 
DBI or the DBD driver, which actually do pretty fancy stuff :-)

Lionel.