Bug ID |
9388
|
Summary |
PC freezes when loading a capture file
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.10.3
|
Hardware |
x86-64
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
Wireshark
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 12028 [details]
Traces taken on a customer site with SIP calls
Build Information:
Version 1.10.3 (SVN Rev 53022 from /trunk-1.10)
Copyright 1998-2013 Gerald Combs <[email protected]> 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.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.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 Nov 1 2013), with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, with 3975MB of physical
memory.
--
Hello,
I have a problem with a particular trace file, my laptop freezes when I try to
open it and I have to switch off/on to restart the PC.
The problem occurs on my PC (running Windows 7 64-bit) with different builds :
1.8.10 32-bit, 1.10.3 32 & 64-bit.
I have no problem when I open that file on my laptop using build 1.8.6 32-bit.
I opened the same file with another PC (running Windows 7 SP1 32-bit) : with
build 1.8.9 32-bit it was OK, but with build 1.10.3 32-bit I have an error
message "Wireshark has run out of memory" (here PC doesn't freeze and I can
close the application).
Regards,
Alain
You are receiving this mail because:
- You are watching all bug changes.