Re: How to debug GC leak

2017-12-18 Thread Andrew Benton via Digitalmars-d-learn 

On Monday, 18 December 2017 at 07:03:14 UTC, Andrew Benton wrote:

[snip]


Looking at dmd's gc profile, it looks like only 
std.array.Appender!string has allocated enough to be the culprit. 
End program memory was 110MB and the Appender!string had 
allocated 127MB totaly with Appender!(Json[]) coming in second at 
5.1MB.

How to debug GC leak

2017-12-17 Thread Andrew Benton via Digitalmars-d-learn 
I'm looking for a memory leak in my use of vibe.d JSON objects.  
The gc profiler built into the runtime only shows allocation 
count and allocation bytes, so I can make guesses around what 
might have leaked, but I can't be sure where or when, or exactly 
what leaked.


I'm sure someone else has run into this problem before.  How did 
you solve it?  I had hoped to also get a view into what was freed 
and when.