Re: leaking memory on shutdown

[Jakub Zawadzki <darkjames-ws () darkjames pl>]

Hi,

On Thu, Jun 27, 2013 at 08:22:27PM -0400, Evan Huus wrote:
> On Thu, Jun 27, 2013 at 5:25 PM, Jeff Morriss <jeff.morriss.ws () gmail com> wrote:
> > [Taking discussion out of the bug since it's not specifically related to
> > that bug.]
> >
> > But, more seriously, Guy pointed out a (long?) while ago that a certain OS
> > from a company he knows well has a way for applications to tell the OS
> > something like "I have nothing to save before exiting" and when that flag is
> > set and the user closes the app, the OS kills it with SIGKILL: it's faster
> > and simpler that way.  It's an interesting concept...  It makes me think
> > that we shouldn't really be spending time trying to fix leaks on shutdown.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4140#c16 ;-)

> The one benefit of fixing leaks on shutdown is that it makes it a
> million times easier to detect other (real) leaks because valgrind's
> output becomes useful. Right now any valgrind run you do with
> --leak-check=full is painfully difficult to analyze because of all the
> garbage (and dynamic hf arrays) that count as 'leaks'.

Have you tried creating suppression file?
http://wiki.wxwidgets.org/Valgrind_Suppression_File_Howto
___________________________________________________________________________
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