https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9114
Christopher Maynard <christopher.mayn...@igt.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Christopher Maynard <christopher.mayn...@igt.com> ---
A lot of memory leaks have been found and fixed in Wireshark since this bug was
filed, and there are tools, such as asan, that continue to help catch/plug
leaks; it's basically a never-ending, ongoing process.
I do believe the worst of the memory leaks have been fixed for a long time
though and in any case, since 1.10.0 is no longer supported, nor is the GTK+
UI, I'm closing the bug as fixed. If more memory leaks are found with the
latest stable version of Wireshark and the Qt UI, then they will most likely be
found and fixed anyway, so I don't think there's any point in keeping this bug
open.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
