-
Notifications
You must be signed in to change notification settings - Fork 830
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
Potential memory leak in tcpdump.c #1091
Comments
The first instance is currently at line 2355. Then there is a cleanup block with call to This way, there is indeed some amount of resources not explicitly freed before the exit. Given the number of various ways to allocate these, perhaps the best potential way to address this would be to have a separate resource deallocation function that Until anybody is willing to implement that, the resources will be freed automatically upon the termination of the process. If you are aware of more severe practical effects, please explain in detail. |
The |
Calling pcap_compile in tcpdump.c line: 2350 and 2753 without releasing the fcode cause memleak.
when pcap_setfilter fails, there is no pcap_freecode. It's better to fix it.
The text was updated successfully, but these errors were encountered: