gecko-dev/build/valgrind
Andrew Osmond 45ae50555d Bug 1754978 - Part 1. Refactor CompositableHandle infrastructure to allow in-process driven handles. r=sotaro
For WebGPU, we produce the textures in the compositor process and the
content process doesn't need to be that involved except for hooking up
the texture to the display list. Currently this is done via an external
image ID.

Given that WebGPU needs to work with OffscreenCanvas, it would be best
if its display pipeline was consistent whether it was gotten from an
HTMLCanvasElement, OffscreenCanvas on the main thread, or on a worker
thread. As such, using an AsyncImagePipeline would be best.

However there is no real need to bounce the handles across process
boundaries. Hence this patch which adds CompositableInProcessManager.
This static class is responsible for collecting WebRenderImageHost
objects backed by TextureHost objects which do not leave the compositor
process. This will allow WebGPUParent to schedule compositions directly
in future patches.

Differential Revision: https://phabricator.services.mozilla.com/D138588
2022-02-18 15:59:12 +00:00
..
__init__.py
cross-architecture.sup Bug 1744212 - Add ellipsis to valgrind suppressions. r=emilio 2021-12-03 12:49:04 +00:00
i386-pc-linux-gnu.sup
mach_commands.py Bug 1750599 - Keep track of the time spent running valgrind on perfherder. r=firefox-build-system-reviewers,mhentges 2022-01-19 22:27:48 +00:00
output_handler.py Bug 1654103: Standardize on Black for Python code in `mozilla-central`. 2020-10-26 18:34:53 +00:00
x86_64-pc-linux-gnu.sup Bug 1754978 - Part 1. Refactor CompositableHandle infrastructure to allow in-process driven handles. r=sotaro 2022-02-18 15:59:12 +00:00