mitmdump --version
Mitmproxy: 11.0.0 binary
Python: 3.12.6
OpenSSL: OpenSSL 3.3.2 3 Sep 2024
Platform: Windows-2016Server-10.0.14393-SP0

The specific situation is that I started the following command to receive a large number of packets and filter packet bodies through the local agent, and then used it frequently for a period of time, about a few hours, before it automatically froze. Unknown reason

mitmdump -s your_script.py -p 9090 --ssl-insecure

02:06:40.213][127.0.0.1:55476] server disconnect xxx..xx:443 (219.xx.xx.139:443)
[02:06:42.251][127.0.0.1:55476] client disconnect
[02:06:42.266][127.0.0.1:55448] client disconnect
[02:06:42.266][127.0.0.1:55443] client disconnect
[02:06:42.266][127.0.0.1:55910] client disconnect
[02:06:42.266][127.0.0.1:55970] client disconnect
[02:06:42.266][127.0.0.1:55448] server disconnect xxx..xx:443 (219.xx.xx.139:443)
[02:06:42.266][127.0.0.1:55970] server disconnect xxx..xx:443 (219.xx.xx.139:443)
[02:06:42.266][127.0.0.1:55992] client disconnect
[02:06:42.266][127.0.0.1:56009] client disconnect
[02:06:42.266][127.0.0.1:55992] server disconnect xxx..xx:443 (219.xx.xx.139:443)
[02:06:42.266][127.0.0.1:56009] server disconnect xxx..xx:443 (219.xx.xx.139:443)

It was a sudden situation during normal use, a bit like a dead loop, but I was able to use it normally for several hours and suddenly it appeared without any error for some reason. It just stuck like this, and I had to press Ctrl+C to end it and restart it to be normal. This situation has already occurred, and the specific lag situation is for use http://127.0.0.1:9090 Proxy, timeout and no response, as shown in the above picture, will remain stuck on this interface

The CPU is shown in the following figure, with port 9090 open. However, when proxy 9090 is used, it timeout occurs, and there are no changes or errors in the terminal interface