Wireshark-bugs: [Wireshark-bugs] [Bug 8158] New: Memory leak
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 02 Jan 2013 15:34:25 +0000
Bug ID 8158
Summary Memory leak
Classification Unclassified
Product Wireshark
Version 1.8.4
Hardware x86
OS Windows XP
Status UNCONFIRMED
Severity Critical
Priority Low
Component Wireshark
Assignee bugzilla-admin@wireshark.org
Reporter mauro@mauropellizzer.com 

Created attachment 9753 [details]
Fail after 1500MB of memory, there are only 4 packet in the capture

Build Information:

--
After restarting a capture the memory used by the packets erased is not freed.
For example:
- Wireshark start using around 64KB of memory;
- After few minutes wireshark use 800MB, time to restart in order to not fill
up the memory;
- But after the restart the memory is the same and each new packets Wireshark
gain memory.

This lead to a Visual C++ error when the system fail the next malloc, the only
option that I have found is restart the program, even change interface does not
change anything.

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