Hi Ulan,
Thanks for the response. I will do that over next couple days. It could be
an edge case or could be related to something stupid I am doing when
running isolates on threads in the same process
(https://github.com/just-js/just/blob/main/just.cc#L2722). When i use
separate processes I do
Hi Andrew!
Could you please file a bug at crbug.com/v8 with steps to reproduce? We
will take a look and see if we can optimize this case.
Until it is fixed, I think caching the backing store pointer in the
internal field would work. Then you'd need to ensure that you keep a handle
to ArrayBuffer
Hi,
I have put some details here on an issue i have come across while doing
some
benchmarking:
https://gist.github.com/billywhizz/ff4c83c37142198d2e70992e438bf045
I have a few questions around this:
1) Do we need a pthread_mutex_lock and pthread_mutex_unlock in every access
to ArrayBuffer->G
