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: Mon, 16 Nov 2015 19:52:16 +0000

Comment # 8 on bug 11702 from
From an email from Pascal Quantin:

Here is the call stack:
     Wireshark.exe!pipe_read_bytes(int pipe_fd, char * bytes, int required,
char * * msg) Line 1541    C
     Wireshark.exe!pipe_read_block(int pipe_fd, char * indicator, int len, char
* msg, char * * err_msg) Line 1648    C
     Wireshark.exe!sync_interface_stats_open(int * data_read_fd, void * *
fork_child, char * * msg, void (void) * update_cb) Line 1410    C
     Wireshark.exe!capture_stat_start(capture_options_tag * capture_opts) Line
671    C
     Wireshark.exe!InterfaceTree::updateStatistics() Line 288    C++
     Wireshark.exe!InterfaceTree::qt_static_metacall(QObject * _o,
QMetaObject::Call _c, int _id, void * * _a) Line 107    C++

Each time the sparklines timer expires, we are calling this call stack and
presumably we are leaking the file descriptors in sync_pipe_open_command().
To reproduce it, either install WinPcap or Npcap and open then close a capture
file: the leak will stat from here.

But I just realized that it also happens when starting Wireshark without
WinPcap or Npcap installed (that's what the bug reporter was doing): in that
case in the GUI you see the message telling that WinPcap installation was
detected and no interface is available but in the debug console you can see the
EOF error in pipe_read_bytes().


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