Bug ID |
9914
|
Summary |
Wireshark GUI memory leak
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.10.6
|
Hardware |
x86
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Medium
|
Component |
Wireshark
|
Assignee |
bugzilla-admin@wireshark.org
|
Reporter |
dankots@gmail.com
|
Build Information:
Version 1.10.6 (v1.10.6 from master-1.10)
Copyright 1998-2014 Gerald Combs <gerald@wireshark.org> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Mar 7 2014), with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
AMD Opteron(tm) Processor 6378 , with 8355MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
This sounds exactly what what was reported as resolved by BUG 7775
I am viewing captured packets in Wireshark GUI, either by capturing and
stopping the capture, or by loading an existing capture file from disk.
I'm looking at the Wireshark process memory usage (windows task manager)
The memory usage goes up every time the GUI has to draw something new. If I
select a different packet to view, the memory use goes up, if I select the
first packet, the memory use goes up.
If I alt-tab to another application, the memory use goes up. when I minimize
and maximize, the memory use goes up.
When the memory use exceeds the memory available in my computer, Wireshark
crashes.
You are receiving this mail because:
- You are watching all bug changes.