-
-
Notifications
You must be signed in to change notification settings - Fork 34
Description
Hello @sourcefrog ,
We've encountered a potential issue related to memory allocation when dealing with large packages, specifically observed with the stackslib package from the stacks repository. During a complete mutants run on stackslib, the process halted after processing 7355 out of 11k.
One hypothesis for this behavior is that the memory allocated for each mutant run is not being properly deallocated upon completion. This could result in an accumulated memory usage, leading to an excessive demand for RAM as the process progresses, particularly noticeable in larger packages like stackslib.
Can you please confirm if there's a memory deallocation issue with completed mutant runs? Any insights or suggestions on this matter would be highly appreciated.
We also want to run this for the remaining mutants, without re-running the mutants done already. Is there a straightforward method to run this?
Specs:
32vcpu, 64GB ram, 2TB nvme storage
