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

MemoryErrors and failure to allocate memory #35

Open
devdanzin opened this issue Nov 21, 2024 · 0 comments
Open

MemoryErrors and failure to allocate memory #35

devdanzin opened this issue Nov 21, 2024 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@devdanzin
Copy link
Owner

devdanzin commented Nov 21, 2024

On machines with more cores, running multiple fusil instances in parallel often causes some of them to be unable to allocate memory and delete session directories.

Edit: also happens when running a single instance in a machine. When the fuzzer starts in this state, only a couple of Python modules have been found.

The failure to allocate memory can begin at the start of the instance, or develop after it's running for a while.

Investigate whether raising the memory limit alleviates the issue. Also consider detecting this state and bailing out.

@devdanzin devdanzin added the bug Something isn't working label Nov 21, 2024
@devdanzin devdanzin added this to the 1.7 milestone Nov 21, 2024
@devdanzin devdanzin self-assigned this Nov 21, 2024
@devdanzin devdanzin changed the title `MemoryError´s and failure to allocate memory when running multiple instances MemoryErrors and failure to allocate memory when running multiple instances Nov 21, 2024
@devdanzin devdanzin changed the title MemoryErrors and failure to allocate memory when running multiple instances MemoryErrors and failure to allocate memory Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant