Re: [whatwg] Canvas in Workers

• From: Justin Novosad <junov@chromium.org>
• Date: Wed, 9 Jan 2013 15:01:38 -0500
• To: Stephen White <senorblanco@chromium.org>
• Cc: Gregg Tavares <gman@google.com>, Rick Waldron <waldron.rick@gmail.com>, Elliott Sprehn <esprehn@chromium.org>, Ian Hickson <ian@hixie.ch>, WHAT Working Group <whatwg@whatwg.org>
• Message-ID: <CABpaAqS40oWXoe1MNV0+T0A2ZWSQtDh+nf93DD8QK5M1O2X7-w@mail.gmail.com>

On Wed, Jan 9, 2013 at 2:50 PM, Stephen White <senorblanco@chromium.org>wrote:

>
>
> Currently, to lower the VRAM footprint and improve performance, we don't do
> a copy in 2d canvas.  We temporarily transfer ownership of the texture to
> the compositor at commit time, and block the renderer until the composite
> is complete.  That may change, however.
>
> Stephen
>
>
To be more accurate, the renderer only blocks if it needs to access the
texture, for example if getImageData is called before the composite is
complete. All write operations are non-blocking because they can be
recorded an deferred until the composite is complete.

>
>

Received on Wednesday, 9 January 2013 20:02:06 UTC