[fuchsia] Decommit discardable memory without relying on the VMO handle.
DiscardableSharedMemory::Purge() attempts to proactively de-commit pages once the instance is unused, to free it quickly even if the peer is slow to unmap it. However, the DiscardableSharedMemoryManager (typically in the browser) maps instances but then closes their handles - Purge() must therefore be implemented without reference to the handle. Bug: 1023693 Change-Id: Ic645232c0b24d85acb64e915bbef05804b25b001 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1912698 Commit-Queue: Daniel Cheng <dcheng@chromium.org> Reviewed-by:Daniel Cheng <dcheng@chromium.org> Auto-Submit: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#715865}
Showing
Please register or sign in to comment