Closed edre closed 1 year ago
As described in #15, this issue may be resolved by actually initializing the extremely important coords system. Can you see if you can still reproduce it? (I haven't yet been able to.)
I now get a different out of bounds read. See https://github.com/richardjs/zoe/issues/15#issuecomment-1548915259
I believe this is solved--see explanation in #15. But let me know if you still encounter the issue.
Seen in worker launched from bestmove:
0 bytes after a 1-byte region sounds like it's probably dereferencing a pointer returned from a malloc(0). In the context of Node_expand, that would be a node with zero children. The game state definitely had moves available so I don't know.