Wireshark-bugs: [Wireshark-bugs] [Bug 1024] New: 0.99.2 crashes on big/long capture
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 31 Jul 2006 01:03:27 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1024

           Summary: 0.99.2 crashes on big/long capture
           Product: Wireshark
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: graeme.nelson@xxxxxxxxxxxxxxxxxxxx


Leaving WireShark capturing for a few hours seems to cause it to crash. I have
had this happen twice so far.

First time: set it to capture for 18 hours, and it had been capturing for
3:58:19 (h:m:s) before it had a "windows" crash (Dr.Watson type thing that
WinXP does).  Left me with a file in my temp directory called "etherXXXXVZIOCT"
will a length of 30,917,118 bytes.  Was using WireShark 0.99.2pre1.

Second time: set it to capture for about 150 minutes and to save to files,
creating a new file every 10MB with the base filename of "PRL 28-7-2006". 
After just over 2 hours it bombed (as described above), leaving me with to
files: "PRL 28-7-2006_00003_20060728140108.pcap" with a length of 10,485,834
bytes and "PRL 28-7-2006_00004_20060728143008.pcap" with a length of 7,727,579
bytes.  There was no sign of 0001 and 0002 files.  Was using WireShark 0.99.2.

There was a few GB of available hard disk space on both occasions.  The
hardware was a HP Compaq nx7010 laptop with 512MB RAM running WinXP SP2. 
WinPCap 3.1. WireShark was installed within Altiris SVS 2.0.1336.

Please let me know what other info you want.


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