Wireshark-bugs: [Wireshark-bugs] [Bug 7676] tshark -q -z io, stat, 1 causes core dump for files

Date: Sun, 2 Sep 2012 14:44:25 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7676

Jakub Zawadzki <darkjames-ws@xxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |darkjames-ws@xxxxxxxxxxxx
         OS/Version|Windows XP                  |FreeBSD

--- Comment #6 from Jakub Zawadzki <darkjames-ws@xxxxxxxxxxxx> 2012-09-02 14:44:24 PDT ---
(In reply to comment #5)
> FreeBSD 'time' doesn't give any memory stats, but I ran it anyway:

I think it should with -l option:
  -l      The contents of the rusage structure are printed as well.
  (From: http://www.manpages.info/freebsd/time.1.html)

> [steve@nms231s1 ~]$ time -p tshark -n -r 20120214-BA_00001_20120214155239.pcap
> -q -z io,stat,1
> 
> [...]
> 
> At the same time, I ran this in another console to give you an idea of the
> memory usage:
> 
> [steve@nms231s1 ~]$ top -b -d40 -s1 | grep 'tshark\|PID'
> 65525 steve            1  25    0 85176K 42864K vnread  0   0:00  2.20% tshark
> 65525 steve            1  39    0   269M   226M CPU0    0   0:01  8.59% tshark
> ...
> 65525 steve            1  48    0  2933M  2662M CPU0    0   0:11 29.30% tshark
> 65525 steve            1  52    0  2933M  2662M wdrain  1   0:11 32.47% tshark
> 
> SIZE is the total size of the process (text, data, and stack), RES is the
> current amount of resident memory (both SIZE and RES are given in kilobytes)

> I've uploaded the BA_00001_20120214155239.pcap file.

Thanks for uploading it, still I can't reproduce the problem.
On my Linux/AMD64 tshark (r44719) use *only* 307 MB:

$ /usr/bin/time -v ./tshark -n -r /tmp/20120214-BA_00001_20120214155239.pcap -q
-z io,stat,1 > /dev/null
        [...]
        Maximum resident set size (kbytes): 307264
        [...]

I really don't know why your tshark takes almost 3GB, any custom plugins?
dissectors? Special configuration?

Can you test if older version of tshark (1.6.x, 1.4.x) has the same problem?
What's memory usage without stats? (i.e. tshark -n -r
20120214-BA_00001_20120214155239.pcap -q)

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