Background When I
used Wireshark to capture the packet, I found that after selecting the network card, it was stuck for a while, and then the process did not respond, reopened and repeated stuck and crashed, the computer stuck, and the task manager was opened and the memory occupied by Wireshark was found to be fast The increase of 1G is more, and I feel that this is abnormal. I checked it online and found that it was related to TLS. Because when I set up webrtc before, I configured the decryption of https without restoring the configuration, and then my browser has not been closed for a long time, causing the browser's sslkeylogfile to become very large, and when Wireshark starts to capture packets, it will read the content of sslkeylogflie in a loop. So it’s stuck and crashed
Solution Method
1:
Restart the browser and delete sslkeylogflie
Method 2:
Delete Wireshark's TLS configuration, in Wireshark Edit->Preferences->Protocols->TLS
Reference material
"Dive into Windbg series" Wireshark's stuck and collapsed
——————————————
Copyright statement: This article is the original article of the CSDN blogger "Black Pepper and Salt", follow CC 4.0 BY-SA copyright agreement, please attach the original source link and this statement for reprinting.
Original link: https://blog.csdn.net/qq_32320399/java/article/details/90441268