Luke,
  After a while of debugging I found a bunch of objects that were being 
created that apparently contain one of the primary keys in one of my 
database tables.  The thing is is the query should only return one result. 
This particular row is hardly ever referenced either.  So now I have found 
a line in my code that is something like you might have been referring to:

      nsEntryId = nsEntryId[0][0]

  That is called quite often, would that cause the object to stay around? 
Is this what you were referring to?

  If not, I'll have to dig a lot deeper and find out why these values are 
scattered all over the object space.

Thanks in advance,
Jason DiCioccio

--On Saturday, November 8, 2003 6:44 AM +0900 "Luke A. Kanies" 
<luke / madstop.com> wrote:

> The last time this happened to me it was because I had a member of a hash
> referring to the parent.  I would assume that that would reliably cause
> memory holes in just about any language.  I would double check your code,
> see if you can find anything.  I resolved the problem by chopping the code
> up until I found the growing part.
>
> Good luck!
>
> Luke
>
> --
> "Greenspun's Tenth Rule of Programming: any sufficiently complicated C
> or Fortran program contains an ad hoc informally-specified bug-ridden
> slow implementation of half of Common Lisp." - Phil Greenspun
>