[Borges-users] memory strikes back!

[Слепнев Владимир]

>If you insert a GC.start at this            ^ location, your memory hole
>will go away. At least it did here.

It didn't for me =) I tried inserting GC.start everywhere. The memory 
does sometimes grow slower, but it's always unbounded. Maybe it's a 
Windows thing?

But even if GC.start did help you... the code I posted originally must 
not leak memory. The programmer should not _ever_ have to call 
GC.start just to stop the leaking.

Ruby-talk ignored our plea, so I'll try posting this to ruby-core in a 
couple hours. If no one here objects to that, of course =))

Vladimir Slepnev