ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 4140] emem patches

Date: Wed, 28 Oct 2009 15:41:38 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4140





--- Comment #15 from Jakub Zawadzki <darkjames@xxxxxxxxxxxxxxxx>  2009-10-28 15:41:37 PDT ---
(In reply to comment #13)
> So why do all that work at exit?  Resources private to the application (file
> descriptors, memory on the heap) don't need to be released by the application
> when it exits - all the OSes on which we currently run (various flavors of
> UN*X, Windows) will release them for you.  The less work done on exit, the
> better (to minimize the delay between "quit the application" and its
> disappearance).

Right, but it's still good practice to free all possible resources.
If someone want the fastest exit (and don't care about 'leaks') he can put
return; in the begining of epan_cleanup()

But it'd be still reported by valgrind or other tools which care about such
leaks.


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.