You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found that the issue is due to the limit of the memory size defined in the zkgraph-c compiler. Solution: double the default memory size for now, then we can handle event.data with size ~1.2kb.
Although we can address the memory change in the as side, zkwasm seems has its own memory limit, and is causing prove fail. Need to discuss with Gao. zkgraph-c@e9ec825
turns out this is an OOM, should figure out why does it use that much, before blaming on zkwasm memory limit.
We did turn off gc in zkGraph, but still 1M mem should be enough under this case.
When the Bytes are too large, the toHexString function cannot execute.
Env
Reproduce
npm init zkgraph@latest
npm run compile && npm run exec -- 4940316
Next, there will be the following error message from execue.
The text was updated successfully, but these errors were encountered: