### Is there an existing issue for this? - [x] I have searched the existing issues and added correct labels. ### Description ## Current Behavior If something goes wrong while launching ComfyUI (bug, port in use, bad config (?) ) the webserver process keeps running in the background ## Expected Behavior The process should stop and any error messages should be shown to the user ### Steps To Reproduce: 1. launch another process that occupies ports 5454 and 55056 2. make sure ayon-comfy is configured to use those ports 3. attempt to launch comfy ui 4. the initial "select launch profile window" shows up but the comfyui never launches 6. open the process monitor: full log (warning: its a gets very repetitive after a while) [ayon_comfyui_output_d0cl76bk (1).txt](https://github.com/user-attachments/files/28505157/ayon_comfyui_output_d0cl76bk.1.txt) https://github.com/user-attachments/assets/3275a6bf-1a0e-42a0-8365-67e52f4e82cd ### Additional context: ### Version Version of the server, ayon-core and the addon that's affected ### What platform were you running when you found the bug? Arch Linux You can also provide any additional information relevant to the issue. ### Relevant log output: ```shell ```
Is there an existing issue for this?
Description
Current Behavior
If something goes wrong while launching ComfyUI (bug, port in use, bad config (?) ) the webserver process keeps running in the background
Expected Behavior
The process should stop and any error messages should be shown to the user
Steps To Reproduce:
launch another process that occupies ports 5454 and 55056
make sure ayon-comfy is configured to use those ports
attempt to launch comfy ui
the initial "select launch profile window" shows up but the comfyui never launches
open the process monitor:
full log (warning: its a gets very repetitive after a while)
ayon_comfyui_output_d0cl76bk (1).txt
Peek.2026-06-02.11-57.mp4
Additional context:
Version
Version of the server, ayon-core and the addon that's affected
What platform were you running when you found the bug?
Arch Linux
You can also provide any additional information relevant to the issue.
Relevant log output: