Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 11702] Start, wait and crash

Date: Fri, 13 Nov 2015 11:55:22 +0000

Comment # 4 on bug 11702 from
Hi Jim,

I've tested your proposal. 

After opening a trace file, the logging stopped with:
11:35:52     Main Dbg  Callback: Opened
11:35:52     Main Dbg  Callback: Read started
11:35:52     Main Dbg  Callback: Read finished
11:35:52     Main Dbg  Callback: Opened

Later I closed the file and Wireshark continued with:
11:49:16     Main Dbg  Callback: Closing
11:49:16     Main Dbg  Callback: Closed
11:49:18  Capture Dbg  sync_interface_stats_open
11:49:18  Capture Dbg  sync_pipe_open_command
11:49:18  Capture Dbg  read from pipe 8: EOF (capture closed?)
11:49:18  Capture Dbg  read 8 got an EOF
11:49:18  Capture Dbg  sync_pipe_wait_for_child: wait till child closed
[...]
12:06:31  Capture Dbg  sync_interface_stats_open
12:06:31  Capture Dbg  sync_pipe_open_command
12:06:31  Capture Dbg  read from pipe 2046: EOF (capture closed?)
12:06:31  Capture Dbg  read 2046 got an EOF
12:06:31  Capture Dbg  sync_pipe_wait_for_child: wait till child closed
12:06:31  Capture Dbg  sync_pipe_wait_for_child: capture child closed after
0.000s
12:06:32  Capture Dbg  sync_interface_stats_open
12:06:32  Capture Dbg  sync_pipe_open_command

Wireshark crashed after trying to read from "pipe 2046". Looks like open/close
doesn't change this behavior.

Based on my UNIX experience I would say the pipe is opened but not closed
because the file descriptor number is growing instead of been always the same.

Based on the information provided by SysInternals / Handle.exe you have a leak
in Wireshark:

I've two additional observations:
a) I can't copying the content from the Debug Console. Wireshark has been
installed with administrative permissions, but it runs under my unprivileged
user account.

b) I can't change the console.log.level using the preferences dialog. The state
is "Unknown" and I can't change the log level to 255. See the attached
screenshot "Preferences Dialog". I changed the log level directly within the
"preferences" file.
Should I open a new ticket for this issue?

Regards,
Carsten


You are receiving this mail because:
  • You are watching all bug changes.