This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Wireshark 1.10.0 & 1.10.7 has stopped working: APPCrash

0

I'm running Wireshark win64 1.10.7 on a Windows 2008 server R2 Enterprise SP1. From time to time - randomly the Wireshark program stops working. Sometime first a pop-up is shown first: alt text

Then the following pop-up is shown: alt text

Detailed info: Problem signature: Problem Event Name: APPCRASH Application Name: Wireshark.exe Application Version: 1.10.7.0 Application Timestamp: 53569d96 Fault Module Name: libglib-2.0-0.dll Fault Module Version: 2.34.1.0 Fault Module Timestamp: 508d9e80 Exception Code: 40000015 Exception Offset: 00000000000509c2 OS Version: 6.1.7601.2.1.0.274.10 Locale ID: 2067 Additional Information 1: 26cb Additional Information 2: 26cb520882fc9cea3b5c8c04fa568662 Additional Information 3: 4e5b Additional Information 4: 4e5bdfca931be366a570b86a034f3954

The same problem occurred also in v1.10.0 but the upgrade did not solve the problem.

asked 19 May '14, 06:05

Beesman59's gravatar image

Beesman59
16225
accept rate: 0%


One Answer:

1

answered 19 May '14, 06:07

Jasper's gravatar image

Jasper ♦♦
23.8k551284
accept rate: 18%

If it's a bug you need to try to narrow it down. Does it happen durig live capturing? Does it happen when you have captured a lot of traffic(big file) then it might be the out-of-memory problem. If it happens during live captures the capture file might still be in the tmp dir and you can try to load that into wireshark and see if the crash is reproducible. If it is you can try to edit the file to narrow the problem down to fewer packets and open a bug report and attach the capture file to that bug report if it does not contain private data.

(19 May '14, 07:07) Anders ♦

Oh BTW the recent automated builds contain a GTK fix to a memory leak problem. You could try that to see if it fixes the problem.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9914

(19 May '14, 07:09) Anders ♦