Closed disconnect3d closed 5 years ago
Hi,
thx for the bug report. Yes, ropper needs a lot of memory. This is because of the many strings that are managed by ropper internally, those are necessary to speed up the search, the semantic search etc. I think an option to set the number of processes makes sense.
Hi,
there is a new option, --single
. ropper uses only one process if this option is used.
However, Ropper takes much more time for loading gadgets when only one process is used.
TLDR: Ropper may take enormous amount of memory (e.g. ~4GB for a 200MB binary) and fails on fork with OOM (out of mem):
It would be nice to have an option to either limiting number of proceses or just a single process mode.