Wireshark-bugs: [Wireshark-bugs] [Bug 2573] New: ERROR: Wireshark has encountered a problem and
Date: Tue, 27 May 2008 18:09:44 -0700 (PDT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2573

           Summary: ERROR: Wireshark has encountered a problem and needs to
                    close.
           Product: Wireshark
           Version: 1.0.0
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: High
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: graham.lynas@xxxxxxxxx


Created an attachment (id=1830)
 --> (http://bugs.wireshark.org/bugzilla/attachment.cgi?id=1830)
Microsoft Error Dump Text File

Build Information:
Build Information:
Version 1.0.0

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, without POSIX capabilities, 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 XP Service Pack 2, build 2600, 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.
--
Wireshark left unattended on a WinXP machine crashes giving the windows message
screen to send a report to Microsoft.

I have attached the compatibility setails file that was prepared by WinXP.

SCENARIO:

WinXP acts as proxy.
WinXP has 512Mb RAM.
Capture filter: Host=192.168.x.x (Values Changed)
Use Multi Files
New File after 3599 Seconds
Capture Ring 100 Files

Error Window will appear asking to close and send report to Microsoft, however
dumpcap keeps powering on in the background capturing like a little champion.

Additionally, when I check the "Hidden" windows on my system, there are about 8
Wireshark.exe entries on top of the "visible" wireshark.exe window.

The visible and hidden windows all have the little window in the center of
screen saying "Closing File - Please Wait", yet the previous hours' file has
been successfully saved and released. It also means that although you can bring
the current active capture window to the front, the wireshark.exe window is
modal, so the capture window has no focus, thus you cannot scroll or do
anything with it.

On several occasions, the memory footprint of wireshark has grown from an
initial 9Mb to 112Mb. Not sure if this has to do with the error, just an
observation.

This error results in the inability to use another application until you close
wireshark, and then I lose the data packets transfered between stopping and
starting.

Regards

Graham


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