[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	10893
Summary	Qt Wireshark - Run-time memory footprint grows when displaying Welcome screen
Product	Wireshark
Version	1.99.x (Experimental)
Hardware	x86
OS	Mac OS X 10.8
Status	UNCONFIRMED
Severity	Normal
Priority	Low
Component	Qt UI
Assignee	bugzilla-admin@wireshark.org
Reporter	jyoung@gsu.edu

Build Information:
Version 1.99.2-852-g7ed097c (v1.99.2rc0-852-g7ed097c from unknown)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.3.2, with libpcap, without POSIX capabilities, with
libz 1.2.3, with GLib 2.36.0, with SMI 0.4.8, without c-ares, without ADNS,
with
Lua 5.2, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
without PortAudio, with AirPcap.

Running on Mac OS X 10.8.5, build 12F45 (Darwin 12.5.0), with locale
en_US.UTF-8, with libpcap version 1.1.1, with libz 1.2.5, with GnuTLS 2.12.19,
with Gcrypt 1.5.0, without AirPcap.
      Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz (with SSE4.2)

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).

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

Check the man page and http://www.wireshark.org for more information.
--
On OS X the run-time memory footprint for Qt Wireshark will grow continuously
while simply displaying the Welcome screen.

There are several different ways to display the run-time memory footprint for
applications on OS X.  One can use OS X's Activity Monitor or one can use the
CLI based ps command.

Using the ps -v command in a loop one can easily document the memory footprint
over time.

> while [ 1 ]
> do
>    date
>    ps -p $MYWIRESHARKPID -v
>    sleep 5
> done

The ps -v report includes metrics for the VSZ (virtual size in Kbytes), RSS
(the real memory (resident set) size of the process (in 1024 byte units)) and
%MEM (The percentage of real memory used by this process).

If Qt Wireshark is launched and simply allowed to display the Welcome screen,
after a day or two the system can become sluggish as more and more virtual
memory is consumed.  After a certain amount of time the RSS and %MEM values for
Qt Wireshark will tend to level out, but the VSZ value will continue grow.

Test #1 - Elapsed time ~ 14h31m26s, VSZ delta growth 7988708 Kbytes

> Fri Jan 23 23:23:28 EST 2015
>   PID STAT      TIME  SL  RE PAGEIN      VSZ    RSS   LIM     TSIZ  %CPU %MEM COMMAND
> 14314 S+     0:01.86   0   0      0  2869604 200516     -        0   0.6  1.2 /Applications/Wireshark.app/Contents/MacOS/Wires
<snip>
> Sat Jan 24 13:54:54 EST 2015
>   PID STAT      TIME  SL  RE PAGEIN      VSZ    RSS   LIM     TSIZ  %CPU %MEM COMMAND
> 14314 S+    17:03.07   0   0      0 10858312 6376744     -        0   0.3 38.0 /Applications/Wireshark.app/Contents/MacOS/Wireshark

Test #2 - Elapsed time ~ 53m02s, VSZ delta growth 482600 Kbytes.

> Sun Jan 25 11:43:26 EST 2015
>   PID STAT      TIME  SL  RE PAGEIN      VSZ    RSS   LIM     TSIZ  %CPU %MEM COMMAND
> 22823 S+     0:01.71   0   0      0  2873436 199236     -        0   0.3  1.2 /Applications/Wireshark.app/Contents/MacOS/Wireshark
<snip>
> Sun Jan 25 12:36:28 EST 2015
>   PID STAT      TIME  SL  RE PAGEIN      VSZ    RSS   LIM     TSIZ  %CPU %MEM COMMAND
> 22823 S+     0:41.32   0   0      0  3356036 687580     -        0   0.5  4.1 /Applications/Wireshark.app/Contents/MacOS/Wireshark

If Wireshark has been left running for a few days, when Quit, the Wireshark
process will take several minutes to completely exit as it frees all the
accumulated memory prior to exiting.

---

      You are receiving this mail because:

• You are watching all bug changes.