On Wed, 12 Nov 2014 12:05:25 +0000 thedeemon via Digitalmars-d <[email protected]> wrote:
> On Wednesday, 12 November 2014 at 11:05:11 UTC, ketmar via > Digitalmars-d wrote: > > 734003200 > > address space" (yes, i'm on 32-bit system, GNU/Linux). > > > > the question is: am i doing something wrong here? how can i > > force GC to stop eating my address space and reuse what it > > already has? > > Sure: just make the GC precise, not conservative. ;) > With current GC implementation and array this big chances of > having a word on the stack that looks like a pointer to it and > prevents it from being collected are almost 100%. Just don't > store big arrays in GC heap or switch to 64 bits where the > problem is not that bad since address space is much larger and > chances of false pointers are much smaller. even with NO_INTERIOR the sample keeps failing (yet after more iterations). no, really, there is ALWAYS a pointer exactly to the start of the allocated buffer somewhere? i feel something smelly here.
signature.asc
Description: PGP signature
