[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] OffscreenCanvas and shared resources

WebGL shared resources and OffscreenCanvas are orthogonal. There are
two big issues with enabling resource sharing between WebGL contexts:
guaranteeing that updates to resources that should be seen in another
context are actually seen, and guaranteeing that updates to resources
that should not be seen in another context are not seen. Both of these
behaviors are required in order to ensure portability of code.
Enforcing the second is harder. It would also be crucial to not
adversely impact WebGL's performance in the common case since the
shared resources extension would be really intrusive in the WebGL
implementation. Right now we on the Chrome team are focusing on other


On Fri, Apr 10, 2015 at 9:49 AM, Ashley Gullen <ashley@scirra.com> wrote:
> I for one am looking forwards to having the ability to do async texture
> uploads in WebGL, since it's a cause of jank and currently difficult to work
> around.
> It looks like WebGL will be able to run from a worker via OffscreenCanvas
> (see: https://wiki.whatwg.org/wiki/OffscreenCanvas).
> This means with shared resources, we can have a WebGL context running in a
> worker, post it an image to create a texture from, and then receive back a
> texture that can be used in a latency-sensitive context (e.g. the "main"
> context from the main thread or another worker, where it is necessary to
> render at a steady 60 FPS).
> What's the status of shared resources in WebGL and does it need updating to
> integrate with the upcoming OffscreenCanvas?
> Ashley

You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl