Nicolas Silva [:nical] Reporter
	Description • 10 years ago

With some TextureClient implementations, we run into the issue of having a some shared data serialized on the client side, then the client objetcs is destroyed before the host gets a chance to deserialize it, which means that it receives a handle to data that has been destroyed.
So far it mostly happened in the same-process scenario, with pointers that we pass through ipc as uintptr_t. So we addref it when serializing and release when deserializing. We do ensure that deserialization always happen for each successful serialization.
This is a bit fragile and doesn't work with shared handles such as DXGI handles.

	Nicolas Silva [:nical] Reporter
	Comment 1 • 10 years ago

For now this is fixed on a per-texture-type basis, including DXGI textures.

	Nicolas Silva [:nical] Reporter
	Comment 2 • 9 years ago

Bug 1200595 fixes this.