On Sun, 19 Sep 2004, Johan Holmberg wrote:
>
>
> I think I've found a memory leak in recent versions of Ruby
> (post 1.8.1 versions).
>

The leak was introduced by the following "change-set"
occuring at "2004/07/28 01:22:48".

I guess it is the eval.c changes, but I don't understand the code,
so I hope matz or someone else can pinpoint the problem ...

--------------------------------------------------------------------
date: 2004/07/28 01:22:48;  author: matz;
* env.h: remove argv from ruby_frame.

* eval.c (rb_eval): no more copy on write.

* eval.c (assign): ditto.

* eval.c (rb_call0): can receive *rest by specifying negative
  argc.  (-1 means 0 arg and *rest, -2 means 1 arg and *rest...)

* eval.c (rb_call0): properly set frame's argc counter.

* gc.c (rb_gc_mark_frame): need not to mark frame's argv

* gc.c (run_final): wrong order of data. [ruby-dev:23948]
--------------------------------------------------------------------

/Johan Holmberg