-
Notifications
You must be signed in to change notification settings - Fork 24
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
bincapz OOM'd at 8GB of RAM with a large source tree #204
Comments
I added some profiling and ran
|
My first heap profile didn't yield anything interesting:
Certainly some places where maybe I could save some space by using pointers to struct and re-use variables, but no obvious memory leak yet. I'm going to try it on a more complicated directory next. |
This 100MB sample looks a little more interesting:
|
I'm making some progress in shaving down memory usage using pointers for larger structures, but I'm unconvinced that it will be enough to avoid OOM's. |
I'm pretty sure the memory leak is in the cgo YARA bindings. I can get bincapz to consume 3GB of RAM, but the profile only shows 80MB of RAM usage. I've tried sending the YARA library file descriptors instead of paths, but it showed no memory improvement, and it likely carries a performance hit. |
bincapz consumed. >8GB of RAM using it against a large directory:
bincapz worked on this directory a few weeks ago, though a lot has changed since then.
The text was updated successfully, but these errors were encountered: