[blink/canvas] Add a feature to reclaim transfer memory when hibernating To transfer the snapshot of an hibernated canvas, shared memory must be allocated. It's not freed until the next frame, which thus wastes memory since a renderer hosting an hibernating canvas is in background, and not producing frames. This CL adds a feature to address this. On a 14 inch macbook pro, this saves 29MiB for a single google docs tab, when canvas hibernation is enabled, which is not the case by default. Similar (albeit smaller, since this depends on screen resolution, unless the client has a High-DPI screen) savings should be observed on other platforms. Bug: 1511658 Change-Id: Ic685f6d798c28e3bd84c7d9457ca39a3069930f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5130231 Reviewed-by: Aaron Krajeski <aaronhk@chromium.org> Reviewed-by: Ian Vollick <vollick@chromium.org> Commit-Queue: Benoit Lize <lizeb@chromium.org> Auto-Submit: Benoit Lize <lizeb@chromium.org> Reviewed-by: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/main@{#1253799}
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.