Do not register shared array buffer backing stores with v8
There is a mechanism that registers the size of the backing store of a typed array with v8 if such backing store is used by a typed array in a v8 isolate. This is done so that v8 can properly assess the memory pressure of an isolate in the presence of external allocations. With shared array buffers, we can no longer attribute a buffer to a specific isolate, as it might be used by multiple isolates at the same time. The current implementation tries to work around this by only registering with one isolate but ultimately fails at doing so, leading to false data. As a stop-gap fix, this change disables registering of shared buffers completely to at least keep the data consistent while we design a working solution. Change-Id: Ib007cbad6af80e6c82d6ab809bf14ce95c54fc93 Bug: chromium:877055 Reviewed-on: https://chromium-review.googlesource.com/1186461 Commit-Queue: Stephan Herhut <herhut@chromium.org> Reviewed-by:Kentaro Hara <haraken@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#585527}
Showing
Please register or sign in to comment