From: Jason DiCioccio <jd@...>
Date: 2003-11-18T12:59:01+09:00
Subject: Re: Long-running daemon acquiring giant memory footprint

Greetings,

--On Tuesday, November 18, 2003 2:12 AM +0900 Robert Klemme 
<bob.news@gmx.net> wrote:

>
> "Luke A. Kanies" <luke@madstop.com> schrieb im Newsbeitrag
> news:Pine.GSO.4.51.0311171048090.2656@pixie...
>> On Mon, 17 Nov 2003, Jason DiCioccio wrote:
>>
>> > 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?
>
> Not the old nsEntryId unless nsEntryId[0][0] has a reference to it.

I've tried removing this line and it does indeed appear to be the problem. 
There was no reference from nsEntryId[0][0] back to nsEntryId.  Is this a 
bug?  I don't think it had this problem in ruby 1.6.x, so it appears 
something changed in the handling of arrays between 1.6 and 1.8.


Regards,
-JD-