object-free go boom

Probing for the allocation and freeing of objects in a Ruby process seems like a good way to check for memory leaks. If your object count keeps increasing, somethings not right. But I’ve been foiled. The following code causes a segfault when running the garbage collector in an irb process with the default Ruby installation in Mac OS X Leopard:

Not a new issue at all, though. It’s been documented over at some cool forum. I’m now tracking down the patch that should fixes this issue.

This does however mean that Leopard ships with a “faulty” version of Ruby. Queue sad face.

Now onto tracking object creation over time.