[Webkit-unassigned] [Bug 76715] Refactor plugin drawing to be more data driven

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=76715





--- Comment #18 from David Reveman <reveman at chromium.org>  2012-01-27 11:17:35 PST ---
(In reply to comment #16)
> (In reply to comment #15)
> > I think you'll have to do your own double buffering for it to work correctly with incremental updates. Use two ioSurfaceTextureIds and flip between them for each update.
> 
> From my understanding, this additional complexity has been introduced because we moved the texture creation code off the compositor thread.
> 
> It feels like things could be simplified significantly by moving everything back onto the compositor thread. 
> 
> Is there any advantage to allocating the ioSurfaceTexture on the main thread?

The textures are always allocated on the compositor thread. It's just the management of textures that can be done on the main thread. As you can't use a ManagedTexture for these ioSurfaces, all texture handling has to happen on the compositor thread.

> 
> If I was to leave the allocation of the ioSurfaceTexture on the compositor thread, could I avoid the additional overhead of the ManagedTexture and double buffering?

You shouldn't use ManagedTexture but you still need double buffering to not get artifacts when incremental updates are enabled.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.