On Wednesday, 25 June 2014 at 14:44:22 UTC, John Colvin wrote:
On Tuesday, 24 June 2014 at 10:16:38 UTC, bearophile wrote:
John Colvin:
I'm getting OutOfMemoryErrors on some machines when calling
GC.malloc (or new) for anything large (more than about 1GB),
where core.stdc.malloc works fine.
On Tuesday, 24 June 2014 at 10:16:38 UTC, bearophile wrote:
John Colvin:
I'm getting OutOfMemoryErrors on some machines when calling
GC.malloc (or new) for anything large (more than about 1GB),
where core.stdc.malloc works fine.
I think that when you go in territories where most people have
John Colvin:
I'm getting OutOfMemoryErrors on some machines when calling
GC.malloc (or new) for anything large (more than about 1GB),
where core.stdc.malloc works fine.
I think that when you go in territories where most people have
not done much coding in D, like allocating than 1 GB in one
On Tuesday, 24 June 2014 at 10:06:10 UTC, John Colvin wrote:
I'm getting OutOfMemoryErrors on some machines when calling
GC.malloc (or new) for anything large (more than about 1GB),
where core.stdc.malloc works fine.
Anyone ever come accross this before? I suspect it's related to
some system
I'm getting OutOfMemoryErrors on some machines when calling
GC.malloc (or new) for anything large (more than about 1GB),
where core.stdc.malloc works fine.
Anyone ever come accross this before? I suspect it's related to
some system memory monitor/management as it's only happening to
me on sup
