On Wednesday, 4 December 2019 at 22:51:45 UTC, Steven
Schveighoffer wrote:
I localized that the leak was actually being caused by
websockets. I want to write down my experience because I did some
weird stuff which seems to be working but I want to learn how it
actually make sense and works.
On 12/4/19 5:04 PM, kerdemdemir wrote:
GC.sizeof(cast(void*)object) will be super useful. I will use that.
I also tried GC: --DRT-gcopt=profile:1 already. It provides so little
information.
I need to find out which member AA or array of which object is causing
this memory problem of mine.I am
On Wednesday, 4 December 2019 at 15:38:36 UTC, Steven
Schveighoffer wrote:
On 12/4/19 3:10 AM, Erdem wrote:
I am used to have cool tools like valgrid massif to visualize
the memory usage from C++ but in D it seems I am blind folded
looking for the problem.
Until now I tried:
--vgc option whi
On 12/4/19 3:10 AM, Erdem wrote:
I am used to have cool tools like valgrid massif to visualize the memory
usage from C++ but in D it seems I am blind folded looking for the problem.
Until now I tried:
--vgc option which show million things which makes it not useful
--build=profile-gc
which see
