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 12701] New: Crash when Opening a File using File Open Dial

Date: Wed, 03 Aug 2016 05:13:22 +0000
Bug ID 12701
Summary Crash when Opening a File using File Open Dialog
Product Wireshark
Version 2.0.5
Hardware x86
OS Windows NT
Status UNCONFIRMED
Severity Major
Priority Low
Component GTK+ UI
Assignee [email protected]
Reporter [email protected]

Created attachment 14786 [details]
Screen video capture of crash happening when File Open dialog is used

Build Information:
Version 2.0.5 (v2.0.5-0-ga3be9c6 from master-2.0)

Copyright 1998-2016 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.11.0, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows 10, build 10586, with locale English_United
States.1252, with WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based
on libpcap version 1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with
Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz (with SSE4.2), with 16277MB of
physical
memory.

--
Hi,
The Wireshark GUI crashes when I try to open a capture file using File Open
dialog. 

See attached screen video capture. 

This issue is repeatable all the time. 

I cannot open a new capture file from with in wireshark. I am forced to goto
Windows explorer and double click on the pcap that I want to view.

See error from WIndows Event Viewer:

Faulting application name: Wireshark.exe, version: 2.0.5.0, time stamp:
0x5799014a
Faulting module name: ntdll.dll, version: 10.0.10586.306, time stamp:
0x571af2eb
Exception code: 0xc0000374
Fault offset: 0x00000000000ee6fc
Faulting process id: 0x3c34
Faulting application start time: 0x01d1ed440f7c3fd7
Faulting application path: C:\Program Files\Wireshark\Wireshark.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 206561eb-7a27-4f1a-ade4-35fa497367e7
Faulting package full name: 

Detailed View:

- System 

  - Provider 

   [ Name]  Application Error 

  - EventID 1000 

   [ Qualifiers]  0 

   Level 2 

   Task 100 

   Keywords 0x80000000000000 

  - TimeCreated 

   [ SystemTime]  2016-08-03T05:01:37.591314200Z 

   EventRecordID 15591 

   Channel Application 

   Computer BLR118380N01.clients.dynatrace.org 

   Security 


- EventData 

   Wireshark.exe 
   2.0.5.0 
   5799014a 
   ntdll.dll 
   10.0.10586.306 
   571af2eb 
   c0000374 
   00000000000ee6fc 
   3c34 
   01d1ed440f7c3fd7 
   C:\Program Files\Wireshark\Wireshark.exe 
   C:\WINDOWS\SYSTEM32\ntdll.dll 
   206561eb-7a27-4f1a-ade4-35fa497367e7


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