[Issue 2105] Manual Memory Management for Associative Arrays

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=2105





------- Comment #6 from dsimcha at yahoo.com  2008-05-19 16:06 -------
If by dropping the iterations down, you mean changing the loop counter in
test(), which controls the array size, from 10_000_000 to a smaller number,
this misses the point of this bug.  It only happens on very large arrays.  From
the informal testing I've done, it seems that size in bytes, not size in
elements, is what matters.  This also makes sense in terms of the tentative
diagnosis of this as a conservative GC issue.  If I drop the array size down a
few notches to 5_000_000, the memory size reaches steady state as you describe,
using GDC 2.014.

Also, I tried this code on GDC 0.24 (32-bit) with an array size of 20_000_000
and it seems to work there, even without the scope keyword on the Linux cluster
I'm working on now.  However, I had tried a similar version of this with a GDC
and a dynamic array instead of an associative on my Windows box a while back
and array sizes over about 13_000_000 broke it.  Don't know why this
inconsistency exists.


--