[wasm] "fix" critical memory pressure notification
Previously, we sent a critical low memory pressure notification when attempting to commit WASM code when the code manager was near the limit for total amount of code allocated. https://chromium-review.googlesource.com/c/v8/v8/+/1073412 "fixed" that, but it causes OOMs on Windows. Since we no longer have the isolate on the code manager, and thus cannot send this notification on commit, send the notification upon the next module creation. This is still not optimal, but should fix OOM issues for lots of small modules on Windows. BUG=v8:7845 R=mstarzinger@chromium.org CC=clemensh@chromium.org Change-Id: I6e20d0c1ee9bc6926a83e0c2fbdc9e9e453588ec Reviewed-on: https://chromium-review.googlesource.com/1098921 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#53700}
Showing
Please
register
or
sign in
to comment