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 7073] New: Wireshark becomes non-responsive when doing Exp

Date: Thu, 12 Apr 2012 16:30:10 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7073

           Summary: Wireshark becomes non-responsive when doing
                    Export->Objects->HTTP-> Save All without entering a
                    "name".
           Product: Wireshark
           Version: 1.6.7
          Platform: x86
        OS/Version: Windows 7
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: panamajim@xxxxxxxxxxx


Build Information:
Version 1.6.7 (SVN Rev 41973 from /trunk-1.6)

Copyright 1998-2012 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
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 GTK+ 2.22.1, with GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, without
SMI, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.12.18, with
Gcrypt 1.4.6, without Kerberos, with GeoIP, with PortAudio V19-devel (built Apr 
6 2012), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 21022

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Issue encountered after capturing data or opening previously captured .pcap. 
Attempting to export HTTP objects with Save All option.  If the OK button is
selected without entering text in the Name entry then Wireshark will enter into
a non-responding mode.  Eventually the program must be terminated by selecting
the close button.

Same behavior encountered in 1.7.0 64-bit.

Under the 32-bit version (1.6.7) the same actions will generate a warning
message telling the user to enter a name.  Once text data is entered, the Save
All proceeds normally.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.