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

lowmemorykiller kicks in and ruins all our hard work #3

Open
jduck opened this issue Sep 14, 2015 · 1 comment
Open

lowmemorykiller kicks in and ruins all our hard work #3

jduck opened this issue Sep 14, 2015 · 1 comment

Comments

@jduck
Copy link
Contributor

jduck commented Sep 14, 2015

Once too much memory is used, low memory killer comes in and meddles with our strategy. BOO.

@jduck
Copy link
Contributor Author

jduck commented Sep 17, 2015

This seems to be the biggest source of instability in your exploit. I highly recommend dialing back the aggressive nature of your exploit.

Further, here's more evidence to support reducing memory/cpu usage:

KEEN TEAM ‏@k33nteam Sep 15
@jduck @fi01_IS01 use small chunks, periodically check meminfo and probe ping socks every round, should work well for devices with 1+GB RAM

https://twitter.com/K33nTeam/status/643773431272488961

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

No branches or pull requests

1 participant