- From: Glenn Maynard <glenn@zewt.org>
- Date: Tue, 17 Apr 2012 23:18:34 -0500
On Tue, Apr 17, 2012 at 5:32 PM, Darin Fisher <darin at chromium.org> wrote: > In Chrome at least, getImageData() doesn't actually block to fetch pixels. > The thread is only blocked when the first dereference of the pixel buffer > occurs. I believe this is done so that a getImageData() followed by > putImageData() call will not need to block the calling thread. > This isn't good enough. It gives no way for developers to ensure that they don't access the image data until doing so won't cause a synchronous flush. -- Glenn Maynard
Received on Tuesday, 17 April 2012 21:18:34 UTC