jfs    2025-03-18 👍 👎

Let me repeat what I think I understand.

You edited the file triton-vm/examples/factorial.rs line 38 to be let public_input = PublicInput::from([bfe!(128_000)]);. You then ran the factorial example of Triton VM, for example, with cargo run --example factorial. On a machine with 512 GiB of RAM, the example succeeds. On a machine with 128 GiB of RAM and 32 GiB of swap, the command fails. factorial.rs has 80 lines, so I don’t know what line 96 does.

If you change the input to be 64_000 instead, the command succeeds on both machines. Is that correct?

marco    2025-03-18 👍 👎 [op]

yes，you are right. the line 96 is because i add some commit.

jfs    2025-03-20 👍 👎

I cannot reproduce the behavior you describe. Either the proving step succeeds and the verification step then also succeeds, or the proving step gets cancelled because the machine runs out of memory and the verification step is never executed. Does the commit you added change behavior in some way?

If the problem still exists, would you mind opening an issue on Triton VM’s repository?