Bugs item #8344, was opened at 2007-01-31 18:11
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=8344&group_id=426

Category: Core
Group: 1.8.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Brian Mitchell (binary42)
Assigned to: Nobody (None)
Summary: GC memory explosion

Initial Comment:
This code was derived from a scenario where the GC was disabled to avoid some memory bugs in a third party library. It solved the first problem but created another on specific platforms. The attached file will show the bug on Mac OS X (10.4.8) and ruby 1.8.5-p12. ruby_1_8 from CVS seems to exhibit the same behavior. Other platforms were not tested.

The basic part of the leak is expected. Ruby has always seemed to have issues with reclaiming objects with GC.enable. The problem, in this case, is that GC.enable and GC.start together leak even more memory.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=8344&group_id=426