Currently taking a snapshot of a large heap (close max heap capacity) results in an OOM crash.
There are multiple sources of OOM:
1. DevTools front-end uses the same max heap limit as an ordinary renderer process. We can fix it (at least on x64) by increasing the heap limit for V8 isolate in DevTools.
2. The heap snapshot generator in V8 stores edges in vector-like array (List<T>), which is limited to max 2GB size due to tcmalloc security constraint for chrome.
3. The heap snapshot generator in V8 uses 32-bit ints for indices and ids, which is unsafe for heap snapshots > 2GB. We can fix it by using size_t.
I can look into 1 and maybe 2.
alph@, pfeldman@, how hard would it be to fix 3?
Comment 1 by u...@chromium.org
, Dec 20 2016