LPM: Not so quiet on the western front...

[Janine]

Nope, no evals.

Here's the scoop:

There's a huge select sorted by three fields.  The values in these three
fields are affectionately known as a Big3.  We fetch rows, joining
fields with a tab and pushing the resulting string onto an array, until
the Big3 changes.  At that point, we do "stuff."  Then we undef the
array and start fetching again.  There are about 900 different Big3s.

undef @bigarray is not freeing up memory as I expect.  Watching the
program's memory usage with top, it slowly creeps up and up and up -
even after @bigarray is undef'd.

Right now I'm looking at the "stuff".  Something in there must be
holding on to elements in @bigarray.

*sigh*

Janine


> -----Original Message-----
> From: owner-lexington-pm-list at pm.org
> [mailto:owner-lexington-pm-list at pm.org]On Behalf Of Matt Cashner
> Sent: Monday, July 23, 2001 2:20 PM
> To: lexington-pm-list at happyfunball.pm.org
> Subject: RE: LPM: Not so quiet on the western front...
>
>
> On Mon, 23 Jul 2001, Janine wrote:
>
> > Yeah, debugging and some malloc thinger too.  John (our sysadmin) is
> > going to bump my name to the top of his poop list by the
> end of the day,
> > I'm sure.  ;-)
>
> hunting down big memory leaks in perl is not much fun. mainly because
> perl leaks in a lot of places and it may not be yoru code that's at
> fault. its one of the most frustrating things about working with perl.
>
> OH. are you using eval anywhere? certain scenarios of eval
> leak like my
> head.
>
> --------
> Matt Cashner
> Web Applications Developer
> The Creative Group (http://www.cre8tivegroup.com)
> eek at eekeek.org | Codito, ergo sum
>
>
>