Wireshark-bugs: [Wireshark-bugs] [Bug 11002] Memory of a live capture doesn't get freed
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 24 Feb 2015 12:25:13 +0000

changed bug 11002


What Removed Added
CC   eapache@gmail.com

Comment # 3 on bug 11002 from 
> the "real" memory allocated by emem/wmem will not be returned to the OS when
> a  capture file is closed so Wireshark does not need to allocate the memorry
> again for emem/wmem use

Wmem does make an effort to return memory to the OS at key points, but emem
does not. As this is 1.12 (emem is gone in master) the growth being seen may be
in emem. It's also quite plausible that restarting a live capture wouldn't
trigger a return to the OS anyways, given we're about to need memory again.

And of course, even once we've called `free` or `g_free` on a block, the OS can
do what it likes, including potentially leaving it assigned to wireshark for
the time being for performance reasons.

You are receiving this mail because:
  • You are watching all bug changes.