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

[Bill Meier <wmeier@xxxxxxxxxxx>]

Joshua (Shiwei) Zhao wrote:
> 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


My first guess would be "out of memory".

Please see http://wiki.wireshark.org/KnownBugs/OutOfMemory
for the details.

Note especially the comment about using dumpcap for long-term captures.