new and GC.malloc fail, core.stdc.malloc works

[John Colvin via Digitalmars-d-learn]

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 memory monitor/management as it's only happening to 
> me on supercomputer nodes.

P.S. yes I've checked the return value of core.stdc.malloc. Also, 
I'm not doing anything silly like calling them one after the 
other and then wondering why the second one doesn't work 
(although seeing as I've got ~24GB of RAM to play with that 
shouldn't be a problem).