Re: [go-nuts] syscall/js: strange deadlock caused by wasm event handling callback (runtime bug?)

2022-08-07 Thread atd...@gmail.com
Filed an issue with a reproducer ; https://github.com/golang/go/issues/54328 On Sunday, August 7, 2022 at 12:08:33 AM UTC+2 atd...@gmail.com wrote: > Doesn't seem that this is a known issue. I will try and write a short > reproducer and file an issue. > > On Fri, Aug 5, 2022, 11:18 PM

Re: [go-nuts] syscall/js: strange deadlock caused by wasm event handling callback (runtime bug?)

2022-08-06 Thread at diar
Doesn't seem that this is a known issue. I will try and write a short reproducer and file an issue. On Fri, Aug 5, 2022, 11:18 PM atd...@gmail.com wrote: > Hi, > > I have a little concurrency problem. Seems that my Go-wasm-defined event > handlers run concurrently instead of synchronously. > >

[go-nuts] syscall/js: strange deadlock caused by wasm event handling callback (runtime bug?)

2022-08-05 Thread atd...@gmail.com
Hi, I have a little concurrency problem. Seems that my Go-wasm-defined event handlers run concurrently instead of synchronously. Basically, the event handler is called by runtime.handleEvent which calls into the syscall/js defined version of it Link to source