Re: Freeing memory when quitting Wireshark

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

Hi,

On Tue, Aug 02, 2011 at 01:48:59PM -0700, Alex Lindberg wrote:
> It stays in memory (GUI or tshark version) so that when I run another compile on windows, during the copy of the exe 
> to wireshark-gtk, the build fails with "unable to copy" message.  If I kill wireshark.exe from the task manager, all 
> is good.
>
> If I build the standard WS 1.6.0, all is good, but not with my code included.

Your code is creating any threads?
I think unfinished threads might cause such behaviour or it can be some never ending loop.

Probably the easiest way to find the problem would be to attach debugger after quiting wireshark.

Cheers,
___________________________________________________________________________
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