| Bug ID |
10116
|
| Summary |
Qtshark crashes with seg fault 11 if the I/O Graph window is closed before background processing has completed
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.11.x (Experimental)
|
| Hardware |
x86
|
| OS |
Mac OS X 10.8
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
wireshark 1.11.4-427-g2408297 (v1.11.4-rc1-427-g2408297 from unknown)
Copyright 1998-2014 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 Qt 5.2.1 with GLib 2.36.0, with libpcap, with libz
1.2.3,
without POSIX capabilities, with SMI 0.4.8, without c-ares, without ADNS, with
Lua 5.1, without Python, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT
Kerberos, with GeoIP, without PortAudio, with AirPcap.
Running on Mac OS X 10.8.5, build 12F45 (Darwin 12.5.0), with locale
en_US.UTF-8, with libpcap version 1.1.1, with libz 1.2.5, GnuTLS 2.12.19,
Gcrypt
1.5.0, without AirPcap.
Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz
Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
Qt based Wireshark will crash if the IO Graph window is closed before
background processing has completed.
Using recent buildbot version of Wireshark on OS X which uses Qt UI.
When using the IO Graph feature, if one opens a large enough trace file then
the Qt UI will temporarily display a progress bar in the lower left section of
the main window status bar. If one closes the IO Graph window while the
progress bar is displayed, the IO Window will immediately close, but the
progress bar will continue to update as the retap, recalc or replot processing
apparently continues. When the I/O Graph initiated background processing
completes Wireshark will crashwith Segmentation Fault: 11.
The easiest way to recreate this crash is to open a relatively large file
(perhaps greater than 200MB).
The OS X Crash reporter generally indicates the thread dispatch queue as:
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0 org.wireshark.Wireshark 0x00000001082ac056 IOGraphDialog::updateStatistics() + 232
> 1 org.wireshark.Wireshark 0x00000001084316ee IOGraphDialog::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 380
but the crash report will occasionally list the thread dispatch queue as:
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0 QtWidgets 0x000000010922ed8f QWidget::setFocus(Qt::FocusReason) + 17
> 1 org.wireshark.Wireshark 0x00000001035616ee IOGraphDialog::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 380
I will attach one example of the "IOGraphDialog::updateStatistics() + 232"
crash reports.
You are receiving this mail because:
- You are watching all bug changes.
