Analysis - Stockfish WASMX Issues

Looks fine, though, there are no errors there as far as I can see.

What do you mean? There are 4 threads now with people complainig about "Loading Engine" forever - and moderator bufferunderrun tells us everything is just fine?

I meant his pasbin text looked fine and also that console log didn't list any errors.

Yes, we are aware there issues with WASMX version, though they pop up at random, we are trying to pin point the location, so that we can fix it.

There are no mistakes as far as it works.

But the question is:

"Why does it stop working after a few moves?"

Not quite sure why it shows no errors though because stockfish wouldn't load at that position when i did what you said

Since there are too many issues we'll pause the experiment with the next update and try it again some time later this year.

Chrome users can still opt-in by enabling chrome://flags/#enable-webassembly-threads and users of Firefox Nightly can enable javascript.options.shared_memory in about:config.

Thanks to everyone who reported problems and/or helped debugging.

Can we please leave WASMX? Just make it non-default.