https://issues.dlang.org/show_bug.cgi?id=23483
--- Comment #1 from mw <[email protected]> --- Also, currently in the report profilegc.log only the call stack top allocation site is reported, this is not very useful for things like containers from the common library, e.g. array: void[] std.array.Appender!(char[][]).Appender.ensureAddable.__lambda9 It's much informative to give the full (or top 20 stack traces) to see where the allocation happened in the user code, as what valgrind does. --
