-
Notifications
You must be signed in to change notification settings - Fork 178
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
Unuseful frames should not be stored #19
Comments
You mean the frames on screen, while the scan is still running, right? |
Frames not shown are still stored, yes.
…On Tuesday, August 20, 2019, Shiri ***@***.***> wrote:
You mean the frames on screen, while the scan is still running, right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#19?email_source=notifications&email_token=AHE6CQPKQENN6DNKD2K5Y2TQFO5SZA5CNFSM4INDAQ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4VXVTY#issuecomment-522943183>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHE6CQIKDCZFP7Y4CHLEJQ3QFO5SZANCNFSM4INDAQ4A>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unuseful or disregarded frames should not be stored in memory and disregarded. If i'm doing a handshake attack, it shouldn't eat 16GB of swap for 4 frames listed on-screen after 8 hours of constant attack.
The text was updated successfully, but these errors were encountered: