[Issue 18005] AA leak

[d-bugmail at puremagic.com]

https://issues.dlang.org/show_bug.cgi?id=18005

Rainer Schuetze <r.sagitario at gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |r.sagitario at gmx.de
         Resolution|---                         |FIXED

--- Comment #5 from Rainer Schuetze <r.sagitario at gmx.de> ---
The behavior varies across platforms because it very much depends on the actual
addresses returned by the OS for allocating memory: linux prefers addresses at
the top of the possible addressrange (2^^47) while windows uses returns low
addresses above a couple GB (but not reproducable due to randomization). OSX is
even worse as it starts with very addresses.

In the reporte example, a wide range of low addresses are written into the
(key,value) pairs of an AA. As the key is a string, it contains indirections
that need to be scanned, i.e. the full allocation is scanned by a conservative
GC.

Precise GC to the rescue: when calling the build with "--DRT-gcopt=gc:precise
--DRT-scanDataSeg=precise" as of dmd2.085, even for win32 it behaves as the
linux build.

I guess this is the best we can do, so closing...

--