Great project. I hope the community can make good use of this to make sure the different libraries and gems and pieces of code leak as much memory as possible.<p>Thank you for putting the work in and making Ruby better.
A better title might be "visualizing the object-reference graph in Ruby;" debugging memory leaks is a neat side effect. That being said, it's an interesting little project.
I randomly stumbled across this gist by tenderlove <a href="https://gist.github.com/tenderlove/4576780" rel="nofollow">https://gist.github.com/tenderlove/4576780</a> that displays references as a tree view using d3.js. I think that this gist in particular is pointing out a bug in that the "references" for Fixnums (also Symbols) in an array aren't returned by ObjectSpace.find_references.
Ruby 2.0 has a similar feature built in, although round the other way: ObjectSpace.reachable_objects_from(obj) .. coupled with ObjectSpace.memsize_of() this can be used to do some memory leak analysis.<p>We also get GC.stat[:total_allocated_object] and GC.stat[:total_freed_object]