Comment #13 on issue 2473 by [email protected]:
http://www.chaostoperfection.com/ crashes in V8 initialization on 64-bit
platforms
http://code.google.com/p/v8/issues/detail?id=2473
[email protected]: as you can see in the comments of
https://codereview.chromium.org/11450017/, we were aware of the differences
between allocation and reserving ranges.
Unfortunately, the Linux kernel doesn't provide with a suitable rlimit.
I've also just checked, and unfortunately even flagging the range
MADV_DONTNEED will not remove accounting of the range towards RLIMIT_AS.
I think we should:
1. Use RLIMIT_AS only to deter kernel exploits, by adding a 4G limit on 32
bits process (preventing far calls to 64 bits and large allocation) and
a "very high" limit on 64 bits process (what about 32GB ?)
2. Modify the allocator in tcmalloc to never allocate contiguous ranges of
more than 2GB or something like this.
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
