> We already do that for when checking is enabled, well the GC heuristics > are tuned such that it does not change which is why > --enable-checking=release is always faster than without it.
Right, but it doesn't call ulimit(), so other sources of memory leakage wouldn't be affected. I'm thinking if the gcc driver set a per-process limit of, say, 128M, developers would learn to care about working set performance.
