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.

Sign up for GitHub

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

Jump to bottom

Running a large number of files from a corpus allocates a lot more memory #719

Closed
ggrieco-tob opened this issue Feb 11, 2022 · 2 comments · Fixed by #1002
Closed

Running a large number of files from a corpus allocates a lot more memory #719

ggrieco-tob opened this issue Feb 11, 2022 · 2 comments · Fixed by #1002
Assignees
@arcz
Labels
help wanted

Comments

@ggrieco-tob
Copy link
Member

When the contracts to run are large and the number of sequences of transactions in the corpus is large (e.g. 500), reloading the corpus produces 2x or 3x mores memory than expected.
@ggrieco-tob
Copy link
Member Author

I should re-test this with the current master.

@ggrieco-tob
Copy link
Member Author

This is still an issue, but the amount of usual memory used during normal usage was reduced

@arcz arcz mentioned this issue Mar 29, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arcz arcz

Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Force corpus evaluation crytic/echidna
2 participants
@arcz @ggrieco-tob