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

Fixed bug when having UnknownTcpOption with zero data, avoid extracti… #184

Merged
merged 1 commit into from
Aug 5, 2018

Conversation

shlomikl
Copy link

@shlomikl shlomikl commented Aug 2, 2018

Fixed bug when having UnknownTcpOption with zero data, avoid extracting sub array from the raw data if the length is 2 then what have happened was that there is an attempt to get sub array with length zero (2-2, see the code)

If the length is equal to 2 then it means there is no data, an empty data array will be created.

I had a lot of TCP packets that throws exception due to this issue that eventually caused for increasing the memory, looks like a memory leak...

…ng sub array from the raw data.

If the length is equal to 2 then it means there is no data, an empty data array will be created.
@coveralls
Copy link

Coverage Status

Coverage increased (+8.08%) to 78.35% when pulling 3ba83e4 on shlomikl:v1 into 3846607 on kaitoy:v1.

@kaitoy kaitoy merged commit d35e652 into kaitoy:v1 Aug 5, 2018
@kaitoy
Copy link
Owner

kaitoy commented Aug 5, 2018

Thank you for your contribution!

@shlomikl
Copy link
Author

shlomikl commented Aug 5, 2018

My pleasure Kaito.

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

Successfully merging this pull request may close these issues.

None yet

3 participants