Wireshark-bugs: [Wireshark-bugs] [Bug 7775] New: Wireshark eats too much memory
Date Prev · Date Next · Thread Prev · Thread Next
Date: Sun, 30 Sep 2012 23:48:39 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7775

           Summary: Wireshark eats too much memory
           Product: Wireshark
           Version: 1.8.2
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: aries.nah@xxxxxxxxx


Build Information:
Version 1.8.2 (SVN Rev 44520 from /trunk-1.8)

Copyright 1998-2012 Gerald Combs <gerald@xxxxxxxxxxxxx> 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 (32-bit) with GTK+ 2.24.10, with Cairo 1.10.2, with Pango 1.30.0, with
GLib 2.32.2, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS
2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built Aug 15 2012), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.

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.
--
I've found an algorithm of how to make Wireshark crash:
0. Run TaskManager
1. Capture several packets
2. Select one packet
3. Select next packet
4. Select previous packet
5. Repeat steps 3 & 4 for a long time and look at TaskManager

Wireshark's memory consumption is increasing until it reash 3G and Wireshark
crash.
I think it proves that there is a memory leak in the code.
What do you think?

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.