When quitting gauntlet one process will not get closed

[BennoCrafter]

When quitting gauntlet one specific process will not get closed and every time reopening and quitting gauntlet again adds one.

[BennoCrafter]

When using cargo run, terminating the process in the terminal (e.g., with Ctrl+C) stops everything, but if closed via the system tray, one process remains running.

Steps to Reproduce

1. Run dev command

   cargo run

2. After the process starts, press Ctrl+C in the terminal to stop the process.
   • Expected behavior: The application and all processes should stop.
3. Instead of terminating the process through the terminal, minimize the application and close it via the system tray
   • Unexpected behavior: One process remains running in the background. (activity monitor)

Also it outputs this:

log.log

[Exidex]

Unfortunately, I cannot reproduce this (at least not in dev environment). Gauntlet spawns new processes in 2 cases: opening Settings UI and deno runtime of each plugin runs in separate process. The Settings UI leaving zombie process was fixed in fd48102. For plugin proceses: on Linux it is easy to kill child process when parent process is killed, but on macos there is no such functionality provided by os, so currently we rely on "Broken Pipe" error which will be sent when parent process closes therefore closing connection between server and plugin runtime. This seems to work fine and closes plugin runtime processes, but there may be some edge case where it doesn't happen