Why does this simple test program leak 500MB of RAM?

[FeepingCreature]

On Friday, 30 June 2023 at 18:49:58 UTC, Bastiaan Veelo wrote:
> On Friday, 30 June 2023 at 13:18:12 UTC, FeepingCreature wrote:
>> I think miniscule stack leaks must be keeping large GC pools 
>> alive here.
>
> Just throwing this in here in case it is of significance: Does 
> adding `"--DRT-gcopt=gc:precise"` as a command line option make 
> any difference?
>
> https://dlang.org/spec/garbage.html#precise_gc
>
> -- Bastiaan.

It's never made any difference any time I tried.

I'd expect precise scanning to only be relevant on 32-bit, since 
it doesn't precise scan the stack.

edit: Heh. The precise GC manages to collect *less* garbage in 
the test above, leaving the program standing at 670M residential.

Explain that one. :P