http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2017
------- Comment #4 from jyoung@xxxxxxx 2007-11-27 13:48 GMT -------
Hello Steve,
I've just replicated the problem on my office XP SP1 desktop machine (currently
running Version 0.99.7-SVN-23365 (SVN Rev 23365)) with the trace file attached
to this bug report . It was harder to replicate on my desktop machine than on
my XP and SUSE laptops (it took more tries, more like 7 to 10 attempts) but it
did eventually crash.
I occasionally noticed some "funny things" while repeating steps 2 through 6 on
my Desktop machine.
The temporary pop-up status window that contains the title text similar to "25%
of Refiltering statistics on: all packets" would occasionally contain random
unicode characters for the "Status:" label. The text in the other labels and
values appeared to display/update fine. Seeing the corrupted "Status:" label
did not necessarily predict the crash.
Even more rarely once the "Voip Calls" window was displayed, the value of the
"Stop Time" column, which with the sample trace file normally has the value of
"268.744" would have bogus data. In one case the ".744" was replaced with
".ma".
I assume that the "VoIP Calls" window opens behind the main Wireshark window.
I bring the "VoIP Calls" to the front by clicking on second Wireshark icon on
the Windows Taskbar. I usually wait until the temporary "Refiltering" window
has closed before trying to bring the "VoIP Calls" window to the front. Once
the "VoIP Calls" window is visible I will sometimes see that the value of the
"Stop Time" column changes to its final "268.744" value. When I catch this
post display update its SEEMS more likely the Wireshark will soon crash (but
not always).
I'm thinking this bug is going to be harder to nail down than I originallly
thought. :-(
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.