Issue #649 has been updated by Roger Pack.


You may be able to try and discover why the array is still reachable by applying the "object allocation tracking" stuffs at

http://timetobleed.com/plugging-ruby-memory-leaks-heapstack-dump-patches-to-help-take-out-the-trash/

works for reachability paths, I believe, too [thanks to Aman for the link].
-=R
----------------------------------------
http://redmine.ruby-lang.org/issues/show/649

----------------------------------------
http://redmine.ruby-lang.org