Wireshark exits when a capture is stopped on Windows
Normal capture, the program will automatically exit after pressing stop capture, resulting in unable to save the captured data.
Normal capture, the program will automatically exit after pressing stop capture, resulting in unable to save the captured data.
Please start posting anonymously - your entry will be published after you log in or create a new account.
Asked: 2020-12-21 07:28:07 +0000
Seen: 441 times
Last updated: Dec 21 '20
cannot find "Compare two capture files"
Is it possible to test a capture filter with already captured traffic?
How would I map this display filter to a capture filter?
Can I create a capture filter on a pcap file
Resolve frame subtype and export to csv
On what operating system is this, and what version of Wireshark is this?
Windows 10. Wireshark Version 3.4.2 (v3.4.2-0-ga889cf1b1bf9)
Can you post the contents of the Wireshark menu item Help -> About Wireshark -> Wireshark dialog as there's more info there we need? Also what type of interface are you capturing on?
@grahamb is there some way to determine whether this is a crash, rather than a normal exit, such as a dialog popped up by Windows for an application crash, or an event log search that would find an application crash?
@Guy Harris, if Windows Error Reporting (WER) is enabled, then with most crashes the usual dialog is displayed and something should be logged in the appropriate location. More info about WER here.
If a stack overflow occurs then there may not be any indication, the application can just disappear.