Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 6016] New: Wireshark crashes when capture is stopped and r

Date: Sat, 11 Jun 2011 15:32:47 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6016

           Summary: Wireshark crashes when capture is stopped and
                    restarted after starting with -k switch
           Product: Wireshark
           Version: 1.7.x (Experimental)
          Platform: x86
        OS/Version: Windows Vista
            Status: NEW
          Severity: Major
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: Jim@xxxxxxxxxxxxxxxxx


Build Information:
Version 1.7.0-SVN-37653 (SVN Rev 37653 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 GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, 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
Jun
11 2011), with AirPcap.

Running on 32-bit Windows Vista Service Pack 2, build 6002, 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

--
I normally start Wireshark from a Windows desktop icon that executes the
following:

"C:\Program Files\Wireshark\wireshark.exe" -k -c 100000 -i 1

If I click on the "Stop the running live capture" button, and then click on the
"Start a new live capture button," I get a Windows dialog that says "Wireshark
has stopped working." The dialog gives two choices: "Check online for a
solution and close the program" or simply "Close the program."

Clicking on "View problem details" shows this display:

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    wireshark.exe
  Application Version:    1.7.0.37653
  Application Timestamp:    4df3d444
  Fault Module Name:    MSVCR90.dll
  Fault Module Version:    9.0.30729.5570
  Fault Module Timestamp:    4d2c14d2
  Exception Code:    c0000005
  Exception Offset:    0003b8f0
  OS Version:    6.0.6002.2.2.0.768.3
  Locale ID:    1033
  Additional Information 1:    fd00
  Additional Information 2:    ea6f5fe8924aaa756324d57f87834160
  Additional Information 3:    fd00
  Additional Information 4:    ea6f5fe8924aaa756324d57f87834160

Wireshark does not crash if I remove the "-k" command line switch. I can start
it with either or both of the other command line switches, or with no command
line switches at all and it doesn't crash, but as soon as I add "-k" to the
command line, it crashes when the capturing is stopped and then started again.

The crashing stops if I revert to 1.6.0, and resumes immediately if I reinstall
1.7.0-SVN-37653. I have seen this same behavior in several previous 1.7.0-SVN
versions as well.

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