How to debug long-lived D program memory usage?

[Meta]

On Wednesday, 17 April 2019 at 22:37:38 UTC, Adam D. Ruppe wrote:
> On Wednesday, 17 April 2019 at 19:07:46 UTC, Jacob Carlborg 
> wrote:
>> Perhaps try some of these flags [1] and [2].
>
> oooh, those are very interesting too.
>
> What I was kinda hoping is it would have stats for which file 
> and line of code was responsible for most allocations; a 
> detailed profile. But even so, this is an interesting gem.

Not at all what you want, but it may be useful for figuring out 
where the leaks are. Have you tried compiling with -vgc? 
https://dlang.org/dmd-windows.html#switch-vgc