Hi, I have a need to capture packets continuously (with a filter) in a ring buffer with each file size set to 300Mb and maximum of 4 files. This is all done to capture a particular rare instance of a packet failure. I left my wireshark capture running overnight and then when I came back to look the following morning, the wireshark had crashed and had popped up a Visual Studio 2005 debug dialog to debug the crash. I have v1.8.4 installed in my case. Has anyone experienced this before? What can we do to get around this? asked 24 Jan '13, 16:46  Kasun edited 24 Jan '13, 17:32 |
One Answer:
This is likely to be the known bug of an out of memory error. For any long term capture you should use dumpcap instead of Wireshark. answered 25 Jan '13, 02:01  grahamb ♦ |
I agree that the crash is almost certainly due to running out of memory; however, I would categorize it as expected behavior rather than as a known bug.