Mathieu

> I think the issue was already there in the commit that updates to LLVM 19... Either that or I don't know how to run your tests. I didn't have...

Ok - I re-ran on c866fbf8417cfcf522fd809348a483c5daef2e45, it works, I must've forgotten to clear the cached executor.

> I changed that dependency too, otherwise it wouldn't compile. Both blockifier and your crate pointed to my local folder. I'm surprised, I don't see any compilation error. I edited...

Here's the LLDB trace for the write-after-free issue when running: `cargo test --test tests stStack --no-fail-fast --features "v1,native,ci"` (runs all tests in a single target and filters for stStack) Here,...

LLDB trace when running: `cargo test stStack --features v1,native` (only run the stStack tests) ``` * thread #25, name = 'stStackTests::test_stackOverflowM1DUP_d13g0v0_Cancun', stop reason = signal SIGABRT * frame #0: 0x0000000197ed4764...

I believe it was introduced in https://github.com/lambdaclass/cairo_native/pull/815/commits/4aa739beced8aae5894c8aa2dcaee29bb33589bb I did a run on https://github.com/lambdaclass/cairo_native/pull/815/commits/483726eacfef8cac8ebd27f66f975c2ede2eb49f - fine The next one on https://github.com/lambdaclass/cairo_native/pull/815/commits/47ffbc1b41fefc54df83c17a6eb8283441d67da0 - broken

Fixed 👍

Memory usage looks a lot better - perhaps a few persisting issues?: I am starting a run on CI and will report back in ~1hr I think everything's fine now...

Unfortunately it still fails our CI... I think it consumes too much memory https://github.com/kkrt-labs/kakarot-ssj/actions/runs/11182543855/job/31089141465 There's no explicit shutdown message so I believe we're just hitting a resource limit

https://github.com/lambdaclass/cairo_native/issues/826#issuecomment-2391351065 The max memory usage hit in a run previously (before the snapshot-drop fixes) was ~13Gb, now it's 25Gb which might be too big for our runner. So we probably...