[C#]: 网络请求可能出现死循环问题

[366862732]

检查项 / Checklist

• 我已在 Issues 页面 中搜索，确认了这一 Bug 未被提交过 / I have searched the Issues page and confirmed that this bug has not been reported yet.
• 我确认只是全部选中而没有仔细确认就直接提交了这个 Issue，并且同意这个 Issue 可以直接被关闭 / I confirm that I checked all boxes without carefully reading them, and agree that this issue may be closed directly.
• 我确认正在使用当前更新分支的最新版 PCL CE，若不是，此 Issue 可能会被直接关闭（更新方式：启动器 设置-关于-软件更新 检查更新，或在 Releases 页面下载） / I confirm that I am using the latest PCL CE version on the current update channel. If not, this issue may be closed directly. To update, check for updates in Settings → About → Updates, or download the latest version from the Releases page.
• 我确认会详细描述我所遇到的问题，并附上日志和截图，而不是随便填点东西敷衍了事 / I will describe the problem in detail, attach logs and screenshots, and avoid submitting vague or incomplete information.

描述 / Description

在点击PCLCE中的更新到2.15.0-Beta.4重新启动启动器后发现还是原来的版本，而且重启后点击设置界面会随机卡死（注意截图里是点击了更新之后的，不是没有点）

重现步骤 / Steps to Reproduce

1.打开PCLCE启动器
2.点击右下方按钮重启 PCL CE 以应用软件更新(2.15.0-beta.3→2.15.0-beta.4)
3.再次重启启动器
4.重启启动器后点击设置界面中任意一个选项

日志与附件 / Logs & Attachments

PCL_CE_Logs_20260626212951.zip

[366862732]

把PCLCE 2.15.0 Beta 3设置中的软件更新选项中的自动更新设置的自动更新设置从自动下载并安装更新改成不自动检查更新重启启动器又好了??

[RyogiMutsuki]

[21:29:03.188] [INFO] [.NET TP Worker] [Request] Send request to https://s3.pysio.online/pcl2-ce/apiv2/updates/updates-frx64.json (method = GET, id = 63e571fe-4bb7-46c7-ac36-12b960839ce7)
[21:29:03.188] [DBG] [.NET TP Worker] [Request] Try attempt (id = 63e571fe-4bb7-46c7-ac36-12b960839ce7)
[21:29:03.486] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.574] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.576] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.580] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.589] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.593] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.596] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.597] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.598] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.599] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.599] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.602] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.602] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.606] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.608] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.608] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.611] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.613] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.614] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.616] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.617] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.619] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.620] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.622] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.632] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.634] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.639] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.640] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.645] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230
[21:29:03.654] [DBG] [.NET TP Worker] [HostConnectionHandler] Connected to s3.pysio.online via 172.67.143.230

这里貌似有个死循环，cc @tangge233

[tangge233]

这里输出 Connected to s3.pysio.online via 172.67.143.230 表明已经建立了 TCP 连接，DoH 模块后续的操作不存在导致重复建立连接的死循环。考虑其它模块的问题

[RyogiMutsuki]

目前还是考虑是网络模块的问题，因为这里很明显是重复调用了 ConnectCallback