0x-mesh

0x-mesh copied to clipboard

Augur reported seeing "call to released function" in the logs. Here's an excerpt:

wasm_exec.js:84 {"error_string":"Post http://127.0.0.1:8545: context deadline exceeded","level":"error","msg":"blockwatch.Watcher error encountered","myPeerID":"16Uiu2HAmV1nUZQULquXiQyz2TRPhugpyE92WtAdkksmM6kuFCpk6","time":"2019-12-28T22:54:31-06:00"}
backend.js:6 call to released function
r @ backend.js:6
syscall/js.valueCall @ wasm_exec.js:306
syscall_js.valueCall @ wasm-10107876-2124:1
syscall_js.Value.Call @ wasm-10107876-2103:1
syscall_js.handleEvent @ wasm-10107876-2089:1
runtime.handleEvent @ wasm-10107876-184:1
wasm_pc_f_loop @ wasm-10107876-936:1
wasm_export_resume @ wasm-10107876-935:1
global.Go.class_1._resume @ wasm_exec.js:432
eval @ wasm_exec.js:442

In the logs, call to released function always immediately follows the blockwatch.Wather error.

We know that Post http://127.0.0.1:8545: context deadline exceeded indicates an Ethereum RPC timeout and that call to released function occurs in Go/Wasm code whenever a released function is called. We just need to figure out how these two are related and what exactly is happening.