Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (5494c33 2024-05-30T00:18:10.251370000Z)
What command(s) is the bug in?
forge test (make test)
Operating System
macOS (Apple Silicon)
Describe the bug
With the following PR as an example superform-xyz/superform-core#541
To reproduce
Part 1
- Do
foundryup (latest foundry)
- forge install
- Override RPCs in make file and run
make ftest
- Open Mac activity monitor and check memory usage. This results in a oom:

code 137 in https://github.com/superform-xyz/superform-core/actions/runs/9289996043/job/25566018918
Please note that this is a powerful dedicated Github actions runner, so the memory limits shouldn't actually be reached
Part 2
- Do
foundryup -v nightly-cafc2606a2187a42b236df4aa65f4e8cdfcea970
- forge install
- Override RPCs in make file and run
make ftest
- Open Mac activity monitor and check memory usage

A whopping difference of 36gb.
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (5494c33 2024-05-30T00:18:10.251370000Z)
What command(s) is the bug in?
forge test (make test)
Operating System
macOS (Apple Silicon)
Describe the bug
With the following PR as an example superform-xyz/superform-core#541
To reproduce
Part 1
foundryup(latest foundry)make ftestcode 137 in https://github.com/superform-xyz/superform-core/actions/runs/9289996043/job/25566018918
Please note that this is a powerful dedicated Github actions runner, so the memory limits shouldn't actually be reached
Part 2
foundryup -v nightly-cafc2606a2187a42b236df4aa65f4e8cdfcea970make ftestA whopping difference of 36gb.