From: "Luke A. Kanies" <luke@...>
Date: 2003-11-18T02:02:50+09:00
Subject: Re: Long-running daemon acquiring giant memory footprint

On Tue, 18 Nov 2003, Jason DiCioccio wrote:

> I imagine changing it to:
>
> nsEntryId = nsEntryId[0][0].dup would take care of the problem?  Or just
> using another object name?

Um, I don't really know.  I can't think of a generally good reason to have
an object refer to itself.  Does the object actually need a
self-reference, or are you just reusing the name for convenience?  If it's
just convenience, I definitely recommend using a different name.

Duplication might also solve the problem, but I'm not really sure.  I'm
still a relative ruby newbie and have not figured out all the details of
when you get a reference vs. a copy vs. a real variable.  Others can
hopefully chime in with those answers.

Luke

-- 
:       We are looking at a newspaper clipping labelled "Huffington
: Herald 11/12/96" in which "Huffington" states, in part:
:       "The inhabitants of Tiera del Fuego ... have a single word
: that means 'to look at each other hoping that either will offer to do
: something that both parties desire but are unwilling to do.'"
:       Does anyone know that word?
Management?