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

Wireshark-dev: [Wireshark-dev] Runtime error after a few hours of running

From: "Joshua (Shiwei) Zhao" <swzhao@xxxxxxxxx>
Date: Wed, 4 Feb 2009 16:03:31 -0800
I was running Wireshark to capture WLAN traffic for some long time. Every a few hours it crashes with a runtime error.
With the debug mode, I saw the following error messages:

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

First-chance exception at 0x005ecbdc (libwireshark.dll) in wireshark.exe: 0xC0000005: Access violation reading location 0x046c9000.

The thread 'Win32 Thread' (0x102c) has exited with code 3 (0x3).

The program '[5132] wireshark.exe: Native' has exited with code 3 (0x3).


I was running Wireshark-1.0.4 with winpcap-4.0.2 under winxp.
Can someone give some clue?
 
Many thanks,
Joshua