Wenyong Huang

> > BTW, could you help review PR #2815? Should we add lock for aot_memmove and aot_memset? > > I think the problem with `aot_memmove` and `aot_memset` is similar to...

@eloparco thanks for the clarification! So let's only export the API `wasm_runtime_shared_mem_lock/unlcok`. Could you help review PR #2815?

@eloparco this issue was closed automatically when PR #2834 was merged. I re-open it now.

> Any suggestions on how to debug the problem? Couldn't find anything useful. @eloparco any issue on the AOT?

The aot_memmove should be called by memory.copy opcode, maybe you can check which function has the opcode? It is introduced by the bulk memory feature. BTW, since most of the...

@erxiaozhou the issue was fixed with #3135, please try again. Thanks for reporting the issue.

Close the issue since it had been fixed.

@erxiaozhou the issue was fixed with https://github.com/bytecodealliance/wasm-micro-runtime/pull/3169, please try again. Thanks for spotting the issue!

Close the issue since it had been fixed.

Hi, for the linear memory related APIs exposed (and its internal APIs), I think there may be several questions to discuss: what is type of related linear memory offset arguments/results...