Potential race in getBufferSubDataAsync |
|||||
Issue descriptionIn WebGL2RenderingContextBase.cpp [1]: // TODO(kainino): What would happen if the DOM was suspended when the // promise became resolved? Could another JS task happen between the memcpy // and the promise resolution task, which would see the wrong data? The answer to this question appears to be yes. We need to figure out a way to fix this. AFAIK, it's an innocuous, safe race, so we could potentially change the spec to allow it. [1] https://codereview.chromium.org/2379203002/
,
Nov 4 2016
It's possible to trigger this by using the debugger to pause get-buffer-sub-data-async-stress.html on line 94 (`Promise.all(promises)`...).
,
Nov 28 2016
Lowering to P3 because this entry point doesn't even exist right now.
,
Jan 12 2017
,
Jan 12 2017
,
Feb 3 2017
This entry point exists now as a draft extension, but based on a discussion I had a while ago, I'm pretty sure this race doesn't exist. Reproducing this error using the debugger isn't a real issue. (The debugger can cause otherwise-impossible task execution order.) |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by kbr@chromium.org
, Oct 19 2016