Download Reference Manual
The Developer's Library for D
About Wiki Forums Source Search Contact

Tracing memory -- who is preventing X from being collected?

Moderators: larsivi kris

Posted: 06/29/08 14:29:15

I think there was some discussion about this on a thread in the NG earlier. But are there any GC calls one can make to find out who it is referring to a particular object that's keeping it from getting collected? It would be nice if the GC could at least expose enough of its guts to make it possible to write 3rd party library routines to perform such tasks. Some sort of way to set a hook into the GC's sweep so you can get a callback every time a reference is found to an active GC memory block. If there were such a thing then it would be pretty easy to write some code to find out why a particular object was not collected.


Author Message

Posted: 06/29/08 21:47:51

Could you please create a wishlist ticket from this such that the request doesn't get lost?