From: "Mauricio Fernández" <batsman.geo@...>
Date: 2003-11-09T00:13:45+09:00
Subject: Re: Long-running daemon acquiring giant memory footprint

On Sat, Nov 08, 2003 at 06:44:00AM +0900, Luke A. Kanies 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,

Ruby does mark&sweep, not reference counting; I thus fail to see why
such a structure would fail to be reclaimed.

Do you mean something like
 
  a = {}
  a[:foo] = a

?

-- 
 _           _                             
| |__   __ _| |_ ___ _ __ ___   __ _ _ __  
| '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ 
| |_) | (_| | |_\__ \ | | | | | (_| | | | |
|_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_|
	Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com

Real Men don't make backups.  They upload it via ftp and let the world mirror it.
	-- Linus Torvalds