You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in #217 it would be safe and useful for methods accepting an BufferSource to instead accept an AllowSharedBufferSource.
The argument for safety is that because the ArrayBuffer is already not transferred it is possible for script to modify its contents before the data is sent to the device, allowing this modification to come from another thread is roughly a no-op. In the Chromium implementation in particular, the buffer contents is immediately copied into an IPC message anyways and so the window of opportunity for modification is quite short.
The text was updated successfully, but these errors were encountered:
As mentioned in #217 it would be safe and useful for methods accepting an
BufferSource
to instead accept anAllowSharedBufferSource
.The argument for safety is that because the
ArrayBuffer
is already not transferred it is possible for script to modify its contents before the data is sent to the device, allowing this modification to come from another thread is roughly a no-op. In the Chromium implementation in particular, the buffer contents is immediately copied into an IPC message anyways and so the window of opportunity for modification is quite short.The text was updated successfully, but these errors were encountered: