Wireshark-bugs: [Wireshark-bugs] [Bug 2287] New: memory usage on heavy traffic load

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 20 Feb 2008 15:25:32 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2287

           Summary: memory usage on heavy traffic load
           Product: Wireshark
           Version: 0.99.8
          Platform: PC
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: ernst.vogel@xxxxxxxxxxxx


Build Information:
Version 0.99.8pre1 (SVN Rev 24386)

Copyright 1998-2008 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 with GTK+ 2.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 7.0, with SMI 0.4.5, with ADNS, with Lua 5.1,
with
GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio V19-devel,
with AirPcap.

Running on Windows Server 2003 Service Pack 2, build 3790, with WinPcap version
4.0.2 (packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.

Built using Microsoft Visual C++ 6.0 build 8804

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
We use wirehark on a heavy-load environment (we have the /3Gb switch set in the
boot.ini file to use the maximum amount of memory):

With Wirehark Version 99.6 we can do a trace until the known bug "out of
memory" appears. The memory-usage in the task-manager grows straight
proportional (s. also the picture 99_6_normal_behavior.jpg in the attachment).

Since Version 99.7 & 99.8pre1 we are not able to trace for a longer time.
We have always the fault message "Glib_ERROR **:gmem.c:172:failed to
allocate..". The memory usage grows non-linear (=> see also the picture
99_8_pre1_bug.jpg in the attachment).

Is it possible to correct this in the new versions ?

Thanks & Best Regards
Ernst


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.