On Thu, Apr 10, 2008 at 02:05:17PM +0200, H.Merijn Brand wrote:
> On Thu, 10 Apr 2008 13:00:09 +0200, "Philippe Bruhat (BooK)"
> <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > While looking for memory leaks in our code using Devel::Leak, we
> > pinpointed one of them to a call to selectcol_arrayref
On Thu, Apr 10, 2008 at 03:40:55PM +0100, Tim Bunce wrote:
> I trust the script is destroying the results and, where appropriate,
> the $sth before calling Devel::Leak::CheckSV.
Yes.
The command is run in a block, with lexicals (except the $dbh).
To avoid counting information that is retained by
I trust the script is destroying the results and, where appropriate,
the $sth before calling Devel::Leak::CheckSV.
Could you post the script?
Tim.
On Thu, Apr 10, 2008 at 01:00:09PM +0200, Philippe Bruhat (BooK) wrote:
> Hi,
>
> While looking for memory leaks in our code using Devel::Leak, we
>
On Thu, 10 Apr 2008 13:00:09 +0200, "Philippe Bruhat (BooK)"
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> While looking for memory leaks in our code using Devel::Leak, we
> pinpointed one of them to a call to selectcol_arrayref().
There was also a leak in Text::CSV_XS, which was fixed in version 0.37
I'
Hi,
While looking for memory leaks in our code using Devel::Leak, we
pinpointed one of them to a call to selectcol_arrayref().
The attached script tries several DBI commands on various DBD drivers
(it's easy to add one, or to add code to be tested for leakage), and
reports how much leakage Devel: