https://issues.dlang.org/show_bug.cgi?id=15836
Rainer Schuetze <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Rainer Schuetze <[email protected]> --- The trouble is that the destructor of MemoryStream is calling GC.addrOf in the finalization stage of a collection, and there is a new check that explicitly disallows this. At the sweep stage, the GC is in an intermediate state that might not yield sensible results for GC.addrOf and friends. I think using this as an indicator whether a block of memory is allocated by the GC depends on its exact implementation (block immediately "freed" after finalization?), and it might restrict the inner workings of the GC too much if we make this a requirement. --
