Open Bug 1191523 Opened 11 years ago Updated 3 years ago

Lazily allocate an ImageClient for asynchronous ImageContainers

Categories

(Core :: Graphics: Layers, defect)

Product:
Core
Component:
Graphics: Layers
Version:
29 Branch
Type:
defect

Tracking

()

People

(Reporter: mattwoodrow, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [gfx-noted])

When we have an ImageContainer for an offscreen (or display:none) video, we currently still allocate the ImageClient. This means that we allocate TextureClients, make copies of image data (maybe) etc every time we update the current image. Since the video isn't visible, sharing these things with the compositor is wasteful and uses significant CPU time (destroying texture clients primarily). We should try instantiate this lazily, or make sure we only update the async pieces if we're actually attached to a remote layer.
Whiteboard: [gfx-noted]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.