[sandbox] Treat sandbox reservation failures as OOMs
When the sandbox cannot be initialized, it's either because there is not enough virtual address space available, or because there is not enough memory for the kernel data structures needed for the reservation (this typically happens on Windows 7/8 where reserving virtual memory is expensive). Both cases should be reported as OOMs, not CHECK failures. Bug: chromium:1325302 Change-Id: I17bde9bcd4fbd6e3d54075b8891287c8fb01c1d7 Cq-Include-Trybots: luci.v8.try:v8_linux64_heap_sandbox_dbg_ng,v8_linux_arm64_sim_heap_sandbox_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3688406 Auto-Submit: Samuel Groß <saelo@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#80975}
Showing
Please
register
or
sign in
to comment