Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 10870] Qt Wireshark - Race issue when switching between files using Wireshark'

[bugzilla-daemon@xxxxxxxxxxxxx]

Jim Young changed bug 10870

What	Removed	Added
OS	Mac OS X 10.8	All

Comment # 2 on bug 10870 from Jim Young

Hello Alexis,

I've tested with recent buildbot images from master (Version
2.1.0-3050-g72bba57) on both OS X 10.10.5 and Windows 8.1.

I can easily force an issue on both OSes with even tiny capture files.  
Wireshark will effectively become non-responsive.  Once unresponsive one can
open some menus nut most of items (like Quit Wireshark) will be greyed and
unavailable to select.  Once Wireshark becomes unresponsive top reports
Wireshark consuming 100%.

Interestingly I am not seeing the message box that I reported earlier.  Instead
I see a pair of messages in the console log (On OS X I start wireshark from
terminal window, on Windows I have set preferences to always open a console
window).   Here's an annotated example of what I see on OS X once I've
successfully opened the Files in Set dialog:

> <snip>
> <=== Scroll to new file entry in "File in Set" dialog
> 11:45:48     Main Dbg  Callback: Closing
> 11:45:48     Main Dbg  Callback: Closed
> 11:45:48     Main Dbg  Callback: Opened
> 11:45:48     Main Dbg  Callback: Read started
> 11:45:48     Main Dbg  Callback: Read finished
> <=== Next capture is displayed
> <=== Scroll to new file entry in "File in Set" dialog
> 11:45:49     Main Dbg  Callback: Closing
> 11:45:49     Main Dbg  Callback: Closed
> 11:45:49     Main Dbg  Callback: Opened
> 11:45:49     Main Dbg  Callback: Read started
> 11:45:49     Main Dbg  Callback: Read finished
> <=== Next capture is displayed
> <=== Scroll to new file entry in "File in Set" dialog
> 11:45:50     Main Dbg  Callback: Closing
> 11:45:50     Main Dbg  Callback: Closed
> 11:45:50     Main Dbg  Callback: Opened
> 11:45:51     Main Dbg  Callback: Read started
> 11:45:51     Main Dbg  Callback: Read finished
> <=== Next capture is displayed
> <=== Scroll to new file entry in "File in Set" dialog
> 11:45:51     Main Dbg  Callback: Closing
> 11:45:51     Main Dbg  Callback: Closed
> 11:45:51     Main Dbg  Callback: Opened
> 11:45:51     Main Dbg  Callback: Read started
> <=== Scroll to new file entry in "File in Set" dialog
> 11:45:51  Capture Msg  Capture Stop ...
> 11:45:51     Main Dbg  Callback: capture stopping
> <=== Wireshark starts consuming 100% of CPU
> <=== Scroll to new file entry in "File in Set" dialog
> 11:45:51  Capture Msg  Capture Stop ...
> 11:45:51     Main Dbg  Callback: capture stopping
> <=== Scroll to new file entry in "File in Set" dialog
> 11:45:51  Capture Msg  Capture Stop ...
> 11:45:51     Main Dbg  Callback: capture stopping
> <=== Wireshark terminated from console with CTRL-C.
>^C


Steps to reproduce:

Create a capture fileset.   I created a series of small 2 packet captures by
starting a once-a-second ping to some local target.  Start Wireshark and open
the Capture Options dialog.  On the Input tab select the desired interface (if
not already selected).  Now open the Output tab.  Enter a filename in the
"Capture to a permanent file" (for example pingtest01.pcapng) and set the
option entries to "Create a new file automatically ..." every 1 second.  Start
the capture and let it run run for 60 seconds of so.  This should result in
approximately 60 capture files (depending on when you Stop capturing).  The
last file in the capture set should be displayed.

At this point you should be able to open the "Files in Set" dialog (File | File
Set | List) but for some reason when the Files in Set dialog is opened it
sometimes reports in the title "No files in set" and in the Directory: field
report "No capture opened".  I've submitted Bug 12451 regarding the
inconsistent ability to open the Files in Set dialog.

Once you have successfully opened the "File in Set" dialog and can see a set of
captures start scrolling in the list to select a new capture file.  As you
scroll up and down a new capture file should be presented.   But at some point
if you scroll between multiple files Wireshark will become unresponsive.

---

      You are receiving this mail because:

• You are watching all bug changes.