-
Kevin Modzelewski authored
Previously we would print out all leaked objects at program exit. But this is problematic since it includes both directly leaked objects (the ones we are interested in), and indirectly leaked objects (which only got leaked by being referenced from another leaked object). This uses the cycle collector infrastructure to figure out what objects have non-heap, ie leaked, references remaining. Hopefully this should help us debug cases where there are hundreds of objects remaining.
cbed4274