ElectronNET/Electron.NET

No port protection if application is launched twiced

Open

#971 建立於 2025年12月8日

在 GitHub 查看
 (8 留言) (0 反應) (0 負責人)C# (7,040 star) (710 fork)batch import
bugenhancementhelp wanted

描述

  • Version: 13.5.1 (but confirmed source code was not improved in the latest for this issue)
  • Target: Windows (Windows 11) / MacOS (M Series)

What is happening is that during app startup, Electron Dot Net will inspect open ports to use as a setting for spawning the back-end server. There is a brief window between when the port number is selected, and when the back-end app actually starts up to utilize that port. If another app were to also start up during this time, then you get multiple instances attempting to spawn a back-end server using that same port and configuration. This results in a collision of port usage, causing the app to either crash or lock up.

Steps to Reproduce:

  1. Launch built electron dot net application
  2. Quickly launch a second instance
  3. Note JavaScript exception that appears

貢獻者指南

技術棧
csharpelectronnodejs
領域
desktopbackend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic understanding of Electron.NETFamiliarity with port allocation
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
45
研究方向
Investigate the port selection mechanism in Electron.NET's startup code (likely in the ElectronHost or program entry). Examine the race condition where two instances pick the same port before binding. Consider using a lock or atomic port allocation. Check if there is a mutex or single instance enforcement already; if not, propose adding one.