Closed ppedziwiatr closed 1 year ago
Reading the above issues, it is probably also worth experimenting with isolated-vm version 4.3.6
(which probably requires downgrading the node to ver. 16).
If that won't help - try to temporarily remove the isolate disposal code - https://github.com/warp-contracts/warp-contracts-plugins/blob/main/warp-contracts-ivm-plugin/src/IvmHandlerApi.ts#L85
Downgrading to node 16.18.1, warp 1.2.30, isolated-vm in 4.3.6 works fine
https://github.com/laverdet/isolated-vm/issues/330#issuecomment-1353254772 @janekolszak ? although not sure if we want to use the isolated-vm...
Let's stick with VM2 + separate node process (supplied by the bullmq's sandboxed processors).
With the possible addition of the https://github.com/taskforcesh/bullmq/issues/1555 - it should be 'good enough' for now.
In the future - consider switching to SES.
Probably related to https://github.com/laverdet/isolated-vm/issues/302 https://github.com/laverdet/isolated-vm/issues/307 https://github.com/laverdet/isolated-vm/issues/321
Reproducible example:
In my case it always hangs at 1201. interaction:
We need to generate a stacktrace and report this to library authors.