If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Handle texture deserialization failures

NEW
Unassigned

Status

()

Core
Graphics: Layers
P3
normal
2 years ago
2 months ago

People

(Reporter: nical, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [gfx-noted])

(Reporter)

Description

2 years ago
Currently we assume that we always succeed in deserializing a texture if we succeeded in serializing it.

With bug 1208226 we know that this assumption doesn't always hold true. We can, for instance, fail to map a segment of shared memory if we run out of contiguous address space, and we run into this situation every now and then.

It's not clear to me at which level we should handle it. Maybe allow TextureHost to be in an failure state and notify the child process every time we attach such textures to compositables, in order to know which layer or region we need to invalidate.
(Reporter)

Updated

2 years ago
Whiteboard: [gfx-noted]
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.