Dzmitry Malyshau dcf75e7f03 Bug 1622261 - Refactor the ID recycling to always cycle through the GPU process ... Previously, we kept the object IDs managed on content side only. The GPU side would work with given indices. When an object is destroyed, we'd free the ID on the content side and signal the GPU to delete the object. Problem is that on the GPU process the object may still be kept alive for as long as any dependants are alive. What this change is doing - hooking up the callbacks to the *actual* freeing of IDs on the GPU side. These callbacks end up in messages from WebGPUParent to WebGPUChild, and only then the IDs are freed on the content side and able to be reused. Differential Revision: https://phabricator.services.mozilla.com/D67211 --HG-- extra : moz-landing-system : lando		2020-03-23 07:54:08 +00:00
..
src	Bug 1622261 - Refactor the ID recycling to always cycle through the GPU process	2020-03-23 07:54:08 +00:00
Cargo.toml	Bug 1622846 - WebGPU bindings update to the spec r=jgilbert,webidl,smaug	2020-03-16 21:32:37 +00:00
cbindgen.toml	Bug 1622846 - WebGPU bindings update to the spec r=jgilbert,webidl,smaug	2020-03-16 21:32:37 +00:00