| Bug ID |
9062
|
| Summary |
Visual C++ Runtime Library Error "The application has requested the Runtime to terminate it in an unusual way." when trying to look at Statistics/IO Graph and Flow Graph
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.0
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
ersion 1.10.0 (SVN Rev 49790 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 (32-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, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Jun 5 2013), with AirPcap.
Running on 32-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-2400 CPU @ 3.10GHz, with 3242MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Wireshark appears to work for all other functions. The error occurs only when
trying these two functions. It does not appear to be related to size of
capture. This appears even for just a few lines of captured traffic.
In our environment we have various versions of Visual C++ and we have removed
them to see if there are conflicts but this has not resolved the issue.
There are some instances of Win7 in our environment where the issue does not
manifest.
We have remimaged systems with Win7 and reinstalled Wireshark and still see the
problem.
Is there something I can enable to troubleshoot this problem?
Thanks for your help.
Paul Ybarra
You are receiving this mail because:
- You are watching all bug changes.