Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9114] Memory not released when starting a new capture w/o saving last capture

[bugzilla-daemon@xxxxxxxxxxxxx]

Jeff Morriss changed bug 9114

What	Removed	Added
Status	UNCONFIRMED	RESOLVED
CC		jeff.morriss.ws@gmail.com
Resolution	---	NOTABUG

Comment # 1 on bug 9114 from Jeff Morriss

Wireshark intentionally does not free all the memory it had allocated when
closing a capture file.  It uses its own memory allocator which allows it to
keep (rather large) blocks of memory around for later re-use (when that happens
the memory allocator marks all the memory as "freed" but you won't be able to
see that from any OS utilities: they will simply report Wireshark has still
having allocated however much memory).  Not freeing that memory is an
optimization to avoid having to re-allocate that memory again when the next
file is read.

---

      You are receiving this mail because:

• You are watching all bug changes.