AFAIK the interpreter has no intrinsic leaks, but many ruby applications keep objects referenced beyond their intended life, preventing GC.
Edit: You extended your edit after I started responding :->
perhaps by holding onto objects and not letting the GC collect them
Yup, that's my understanding.
ok if what you say is true then Brad's blog post is just wrong isn't it?. Either he is right or you are.
Holding onto objects sounds like something user code does so "ruby leaks" is (or should be) not correct usage I think.
I use python I don't use Ruby, but "Python leaks", as a claim, is different from "my program written in python leaks memory".
the blog post seems to imply it is Ruby's fault. At least it reads that way ("Ruby leaks") hence my confusion. Thanks for the clarification
EDIT: I stand corrected. It seems like Tom is right and the ruby interpreter leaks memory! Incredible!
This is absolutely hilarious! A process monitor leaks memory and crashes the server. Words fail me!
EDIT: Rub my eyes and read again. Ruby leaks memory? The language (interpreter ? VM? ) leaks memory? That can't be right? He must have meant the application (God) leaks memory (perhaps by holding onto objects and not letting the GC collect them)