Edit

[frame]

On Monday, 5 October 2020 at 11:28:56 UTC, ryuukk_ wrote:
> On Monday, 5 October 2020 at 11:14:47 UTC, frame wrote:
>> So I found out that there is nothing wrong with the method as 
>> in a test environment the allocated memory block is removed 
>> after GC.minimize().
>>
>> Still need to find out why other blocks are not released.
>>
>> However, is there a way to debug currently allocated variables 
>> by the GC?
>
>
> ```
> 	"buildTypes": {
> 	
> 		"debug_gc": {
> 			"buildOptions": ["debugMode", "debugInfo"],
> 			"dflags": ["-profile=gc"]
> 		}
>
> 	},
> ```
>
> and run using: ``dub run --compiler=dmd --build=debug_gc``
>
> once program exit it'll create a log file: ``profilegc.log`` 
> with all allocations

I tried that but it gives me only a profile of used allocations 
over all time. What I really need is a debug feature to see which 
variable/pointer is currently known by the GC or at least which 
one was still referenced by end of the program.