Wireshark-bugs: [Wireshark-bugs] [Bug 6621] New: Wireshark "continually" runs (accordingly to Wi
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 28 Nov 2011 09:39:47 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6621

           Summary: Wireshark "continually" runs (accordingly to Windows
                    Task Manager)
           Product: Wireshark
           Version: 1.7.x (Experimental)
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: mmann78@xxxxxxxxxxxx


Build Information:
Version 1.7.0-SVN-39603 (SVN Rev 39603 from /trunk)

Copyright 1998-2011 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.22.1, with Cairo 1.10.2, with Pango 1.28.3, with
GLib 2.26.1, with WinPcap (version unknown), with libz 1.2.5, without POSIX
capabilities, with threads support, with SMI 0.4.8, with c-ares 1.7.1, with Lua
5.1, without Python, with GnuTLS 2.10.3, with Gcrypt 1.4.6, with MIT Kerberos,
with GeoIP, with PortAudio V19-devel (built Oct 26 2011), 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.10.3, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 21022

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

Check the man page and http://www.wireshark.org for more information.
--
Steps to reproduce:

1. Launch Wireshark and start capture.
2. Apply display filter
3. Stop capture.
4. Switch to other programs (Word, IE), etc so as to not do anything specific
with Wireshark (or any of its "components")


Not sure #2 is required, but even after a stopped capture and with Wireshark
"not in view" (I switched to using other programs), Windows Task Manager still
shows Wireshark continually using 2-9% of the CPU.   Not sure how/why Wireshark
would "idle" like that.

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