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

GUIHorn uses 55 GB of RAM #83

Open
Anonymous941 opened this issue Nov 14, 2024 · 3 comments
Open

GUIHorn uses 55 GB of RAM #83

Anonymous941 opened this issue Nov 14, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@Anonymous941
Copy link

Describe the bug
When analyzing a large binary, I have to make an absurdly large swap file (100 GB) or else it will run out of memory. The combined RAM + swap usage is 55 GB, which seems much higher then intended

To Reproduce
Steps to reproduce the behavior:

  1. Use GUIHorn
  2. See error

Expected behavior
It uses a reasonable amount of RAM

Desktop (please complete the following information):

  • OS: Ubuntu
@Anonymous941 Anonymous941 changed the title GUIHorn using 55 GB of RAM GUIHorn uses 55 GB of RAM Nov 14, 2024
@sei-eschwartz sei-eschwartz added the enhancement New feature or request label Nov 14, 2024
@sei-eschwartz
Copy link

@sei-jgennari do you consider this to be a bug?

@jeffgennari
Copy link

I need more details ... what is the definition of "large program"?

@Anonymous941
Copy link
Author

Anonymous941 commented Nov 16, 2024

I need more details ... what is the definition of "large program"?

It's a ~20 MB firmware image with 430,939 symbols and 49,683 functions. I can send it if it helps (it's released here, but it uses an obscure compression scheme so I can decompress it for you). It just seems that even parsing a large program shouldn't use 50 GB of RAM, and the memory is not freed after the script finishes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants