How to debug long-lived D program memory usage?

[ikod]

On Sunday, 21 April 2019 at 21:04:52 UTC, Patrick Schluter wrote:
> On Thursday, 18 April 2019 at 12:00:10 UTC, ikod wrote:
>> On Wednesday, 17 April 2019 at 16:27:02 UTC, Adam D. Ruppe 
>> wrote:
>>> D programs are a vital part of my home computer 
>>> infrastructure. I run some 60 D processes at almost any 
>>> time.... and have recently been running out of memory.
>>
>> I usually run program under valgrind in this case. Though it 
>> will not help you to debug GC problems, but will cut off 
>> memory leaked malloc-s.
>
> Even valgrind tool=massif ?

I rarely use massif. It is heap profiler, and my primary target 
usually are memory leaks.

Does your question mean that massif can help to debug GC?