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

Wireshark 1.8.0 crash when plotting IO graph

0

Hi all,

My wireshark crashes since I've upgraded to the latest version 1.8.0 when i am trying to plot the retransmission count over time in the IO graph. I got the same error message when trying to plot duplicate ack count over time in the IO graph as well. When i use the earlier stable version (1.6.8), I have no problem. Here is my setup:

  • Windows 7 Enterprise 64bit
  • WinPcap 4.1.2
  • Multiple version of Wireshark (installed) - 1.8.0 (64bit), 1.6.8(64bit), 1.6.5(64bit), 1.4.10(64bit)
  • Some custom profiles that I was using from the earlier Wireshark version in my own personal profile folder

Here is some of the troubleshooting that i've done.

  • Tried removed the custom profile, uninstalled wireshark 1.8.0, uninstalled winpcap and then reinstall back wireshark 1.8.0 with winpcap with the default profile > Same error;
  • Tried installing wireshark 1.8.0 (64bit) on a fresh machine (Windows 7 Enterprise 64bit version) > Same error;
  • Tried installing wireshark 1.8.0 (32bit) on my windows 2003 R2 SP2 server > Same error;

Please find the screenshot of the error message that i am seeing and the graph that I am trying to plot.

alt text

Is it just me having this issue or something has changed that I might not know about? Any advice is very much appreciated.

asked 16 Jul '12, 03:14

thhoong's gravatar image

thhoong
6112
accept rate: 0%


One Answer:

0

Sounds like a bug.

Please file a bug report at bugs.wireshark.org so that it can be tracked and etc.

answered 16 Jul '12, 04:08

Bill%20Meier's gravatar image

Bill Meier ♦♦
3.2k1850
accept rate: 17%

Just to update everyone on this matter.. Where I submitted this bug, there is already a bug reported. If you are interested to follow the status of this issue, please find it in the link below,

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

(16 Jul '12, 05:58) thhoong

Since the answer is that it's a bug, I converted Bill's comment to an Answer.

(23 Jul '12, 06:52) JeffMorriss ♦