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

ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

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

From: bugzilla-daemon@xxxxxxxxxxxxx

Date: Fri, 20 Sep 2013 21:30:16 +0000

Mat changed bug 9114

What	Removed	Added
Status	RESOLVED	UNCONFIRMED
Resolution	NOTABUG	---

Comment # 2 on bug 9114 from Mat

Ok, then the bug is that the memory isn't actually reused.  Upon starting the
next sniff, Wireshark starts allocating more memory immediately. This will
continue until the system runs out of memory.

You are receiving this mail because:

You are watching all bug changes.

References:
- [Wireshark-bugs] [Bug 9114] New: Memory not released when starting a new capture w/o saving last capture
  - From: bugzilla-daemon

Prev by Date: [Wireshark-bugs] [Bug 9169] tshark eats all the memory, fragment_add_work()
Next by Date: [Wireshark-bugs] [Bug 9171] C++ runtime error
Previous by thread: [Wireshark-bugs] [Bug 9114] Memory not released when starting a new capture w/o saving last capture
Next by thread: [Wireshark-bugs] [Bug 9114] Memory not released when starting a new capture w/o saving last capture
Index(es):
- Date
- Thread

© Wireshark Foundation · Privacy Policy

Facebook·Mastodon·Twitter·YouTube