Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

anvil: configure memory limit #7478

Closed
ryanio opened this issue Mar 23, 2024 · 3 comments · Fixed by #7482
Closed

anvil: configure memory limit #7478

ryanio opened this issue Mar 23, 2024 · 3 comments · Fixed by #7482
Labels
first issue A good way to start contributing T-feature Type: feature

Comments

@ryanio
Copy link

ryanio commented Mar 23, 2024

Component

Anvil

Describe the feature you would like

i'm running into EVM error MemoryLimitOOG in anvil. it seems like forge and chisel have --memory-limit flags to configure a larger limit, would it be possible to have this in anvil as well? thank you!

Additional context

No response

@ryanio ryanio added the T-feature Type: feature label Mar 23, 2024
@b68h4
Copy link

b68h4 commented Mar 24, 2024

This a not feature, this is a critical bug! I think need a fastly fix. I cant run transfer function below memory limit.It always print MemoryLimitOOG.

If you reduce the parse_units unit value below 18, MemoryLimitOOG is bypassed. Its so critical bug because i cant transfer tokens truly amount.

Screenshots:
CleanShot 2024-03-24 at 17 32 48
CleanShot 2024-03-24 at 17 33 53

@mattsse
Copy link
Member

mattsse commented Mar 24, 2024

have --memory-limit flags to configure a larger limit, would it be possible to have this in anvil as well

this can be added easily

@mattsse mattsse added the first issue A good way to start contributing label Mar 24, 2024
@mattsse
Copy link
Member

mattsse commented Mar 24, 2024

This a not feature, this is a critical bug! I think need a fastly fix. I cant run transfer function below memory limit.It always print MemoryLimitOOG.

If you reduce the parse_units unit value below 18, MemoryLimitOOG is bypassed. Its so critical bug because i cant transfer tokens truly amount.

Screenshots: CleanShot 2024-03-24 at 17 32 48 CleanShot 2024-03-24 at 17 33 53

this error is thrown when the evm tries to expand past the limit.
because this is related to the input value, it looks like this is due to the transfer implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
first issue A good way to start contributing T-feature Type: feature
Projects
None yet
3 participants