Debugging a Memory Leak

[Maxime Chevalier-Boisvert via Digitalmars-d-learn]

> GC problems are *nasty*. My advice is to run the simplest 
> program you can think of that still exhibits the problem, and 
> then put in printf debugging everywhere to see where it breaks 
> down.
>
> Not sure if this is useful.

Unfortunately, the program doesn't break or crash. It just keeps 
allocating memory that doesn't get freed. There must be some 
false reference somewhere. I'm not sure how I can printf debug my 
way out of that.