[JS Sandbox] Use OOMErrorCallback instead of NearHeapLimitCallback NearHeapLimitCallback isn't meant to handle OOM; it can be eargely called before v8 gives up. OOMErrorCallback seems like the proper hook to throw an exception. Note: I updated v8 in DEPS to test against CQ, this change will be remove once v8 change lands and rolls. https://chromium-review.googlesource.com/c/v8/v8/+/7027934 Bug: 450361757 Change-Id: I0a03ce82513c828e7af64d724f5164240e353d11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7026578 Reviewed-by: Nate Fischer <ntfschr@chromium.org> Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Cr-Commit-Position: refs/heads/main@{#1528264}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.