Wireshark mailing list archives
Re: leaking memory on shutdown
From: Jeff Morriss <jeff.morriss.ws () gmail com>
Date: Fri, 28 Jun 2013 09:57:58 -0400
On 06/28/13 09:21, Evan Huus wrote:
The correct approach, I think, is to fix epan_cleanup() so that it actually cleans up *everything* owned by epan, but then simply not call it if we're about to exit. If there is some cleanup we do need to do, then epan should provide an epan_cleanup_fast() or epan_cleanup_minimal() or similar to call in those cases.
True, good points. Sounds like a good use case for another environment variable (WIRESHARK_CLEAN_UP_ON_EXIT?) which we can set in our test scripts (including the fuzz test script since that cleanup--freeing emem currently--is necessary to detect canary corruption).
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Re: leaking memory on shutdown Jeff Morriss (Jun 27)
- Re: leaking memory on shutdown Evan Huus (Jun 27)
- Re: leaking memory on shutdown Jakub Zawadzki (Jun 27)
- Re: leaking memory on shutdown Evan Huus (Jun 28)
- Re: leaking memory on shutdown Jeff Morriss (Jun 28)
- Re: leaking memory on shutdown Jakub Zawadzki (Jun 27)
- Re: leaking memory on shutdown Evan Huus (Jun 27)