mirror of
https://github.com/Comfy-Org/desktop.git
synced 2026-11-04 23:47:43 +00:00
[GH-ISSUE #1346] [Bug]: flux1 kontext dev generates images, executes to the unet loader, and appears to be reconnecting and cannot continue execution-ComfyUI Setup 0.4.74 - x64 #374
Labels
No labels
area: desktop-app
Bounty
bug
bug-cop:answered
bug-cop:response-received
component: installer
component: preload
custom node
dependencies
Design
documentation
duplicate
enhancement
expected
frontend
good first issue
installation
Low-Priority
performance
Planned
platform: cross-platform
platform: windows
Potential Bug
Potential Bug
pull-request
question
refactor
Release
stale
User Support
V1
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/desktop#374
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @qlxxkj on GitHub (Sep 25, 2025).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1346
App Version
comfyui_destop_0.4.74

Expected Behavior
flux1 kontext dev successfully generates images
Actual Behavior
flux1 kontext dev generates images, executes to the unet loader, and appears to be reconnecting and cannot continue execution.
Steps to Reproduce
Debug Logs
Browser Logs
none
Settings JSON
comfy.settings.json
Other
No response
┆Issue is synchronized with this Notion page by Unito
@dosubot[bot] commented on GitHub (Sep 25, 2025):
The "Reconnecting" issue and execution hang at the Unet loader are most likely caused by missing or broken dependencies—especially the
comfyui-frontend-package—in your Python virtual environment. This is a common problem after upgrading ComfyUI Desktop or installing/updating custom nodes, and is confirmed by the errors in your logs and recent community reports [docs].To fix this, open the built-in terminal in the ComfyUI Desktop app and run:
Make sure you are running this inside the app's virtual environment, not your system Python. This will install all required dependencies, including the frontend package, and should resolve the "Reconnecting" state and allow workflows to execute past the Unet loader [docs].
If the issue persists, try these steps: disable all custom nodes, reset or delete the
.venvfolder to force a clean environment, back up and remove config files (likecomfy.settings.json), and restart the app to let it regenerate fresh configs. These steps address corrupted environments and custom node conflicts, which are frequent causes of execution hangs [issue].Database initialization errors (sqlite3.OperationalError) in your logs do not currently block startup but may affect future features; if you see persistent database errors, check for disk permission issues or clear the database files in your user directory [issue].
Let me know if you need more detailed instructions for any of these steps.
To reply, just mention @dosu.
Docs are dead. Just use Dosu.
@qlxxkj commented on GitHub (Sep 25, 2025):
There is no requirements.txt in ComfyUI Desktop installation directory
@dosubot[bot] commented on GitHub (Sep 25, 2025):
ComfyUI Desktop doesn't put requirements.txt in the main installation directory. Instead, you'll find it in the resources/ComfyUI subdirectory (for example: C:\Users\Administrator\AppData\Local\Programs\ComfyUI\resources\ComfyUI\requirements.txt on Windows). To install or repair dependencies, use the built-in terminal (which opens in the app's virtual environment) and run:
If you don't see requirements.txt there, your installation might be incomplete or corrupted—reinstalling the app usually restores it. For custom nodes, each has its own requirements.txt in its folder under custom_nodes, and ComfyUI Manager typically handles those automatically. More details are in the official docs and related support threads.
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
@qlxxkj commented on GitHub (Sep 25, 2025):
Is it because of the upgrade of pytorch? The current hardware cuda version is 12.4
@dosubot[bot] commented on GitHub (Sep 25, 2025):
Yes, the upgrade to PyTorch 2.8.0 with CUDA 12.9 support could be causing compatibility issues if your system only has CUDA 12.4 drivers. PyTorch CUDA builds are typically only guaranteed to work with the same or newer driver versions, so a mismatch can lead to runtime errors or hangs during execution—like the "Reconnecting" state you’re seeing [docs].
To check and resolve this:
If you need to match PyTorch to your system’s CUDA version, you can uninstall torch and reinstall it with:
(Replace
cu124with the CUDA version your drivers support.)If you continue to see issues, double-check your driver version with:
and make sure it’s compatible with the CUDA version required by your PyTorch build [docs].
Let me know if you need help with any of these steps!
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
@qlxxkj commented on GitHub (Sep 26, 2025):
Comfy Destop automatically installs PyTorch 2.8.0+cu129 with the latest version. I updated my hardware's CUDA to 12.8, but that didn't fix the problem. It can be started normally, but it says "[ComfyUI-Manger] skipped fixing the 'comfyui-fronted-package' dependency because the comfyui is outdated."
@dosubot[bot] commented on GitHub (Sep 26, 2025):
The message about skipping the 'comfyui-frontend-package' dependency because "comfyui is outdated" means the Desktop app's validation logic detected that your ComfyUI core version or environment doesn't meet the requirements for safe dependency updates. This can happen if the core code, virtual environment, or requirements files are mismatched, incomplete, or not fully upgraded. As a result, ComfyUI-Manager won't attempt to fix or install frontend dependencies, which can break workflows and cause issues like the "Reconnecting" hang you described [docs].
To resolve this, make sure your core code and dependencies are fully updated and consistent. In the Desktop app's built-in terminal, run:
If that doesn't fix it, try deleting the
.venvfolder in your ComfyUI directory and restarting the app to force a clean environment and reinstall dependencies. If you still see the "outdated" message, your Desktop version may be lagging behind the latest core and dependency updates—this is a known limitation of the stable Desktop builds [docs]. For the latest features and fixes, consider using the portable or manual install versions, which track development updates more closely.If you need to install a specific dependency manually (like comfyui-frontend-package), check the required version in
resources/ComfyUI/requirements.txtand run:Replace
<version>with the version listed in the requirements file. This should help restore missing frontend functionality and allow your workflows to run past the Unet loader [docs].To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
@qlxxkj commented on GitHub (Sep 26, 2025):
During the execution of the flux_kontex_dev_basic workflow, the log displays:
got prompt
Using pytorch attention in VAE
Using pytorch attention in VAE
VAE load device: cuda:0, offload device: cpu, dtype: torch.bfloat16
Requested to load AutoencodingEngine
loaded completely 11011.0 159.87335777282715 True
Requested to load FluxClipModel_
loaded completely 9.5367431640625e+25 4777.53759765625 True
CLIP/text encoder model load device: cuda:0, offload device: cpu, current: cuda:0, dtype: torch.float16
clip missing: ['text_projection.weight']
……
Execution stops, and the interface displays "Reconnecting"
@qlxxkj commented on GitHub (Sep 26, 2025):
got prompt
Using pytorch attention in VAE
Using pytorch attention in VAE
VAE load device: cuda:0, offload device: cpu, dtype: torch.bfloat16
Requested to load AutoencodingEngine
loaded completely 11011.0 159.87335777282715 True
Requested to load FluxClipModel_
loaded completely 9.5367431640625e+25 4777.53759765625 True
CLIP/text encoder model load device: cuda:0, offload device: cpu, current: cuda:0, dtype: torch.float16
clip missing: ['text_projection.weight']
D:\SD\ComfyUI_windows_portable>pause
@qlxxkj commented on GitHub (Sep 26, 2025):
Now it cannot be repaired, I don't know why, whether I install comfyUI desktop version or ComfyUI_windows_portable.The terminal prints the same error message:
got prompt
Using pytorch attention in VAE
Using pytorch attention in VAE
VAE load device: cuda:0, offload device: cpu, dtype: torch.bfloat16
Requested to load AutoencodingEngine
loaded completely 11011.0 159.87335777282715 True
Requested to load FluxClipModel_
loaded completely 9.5367431640625e+25 4777.53759765625 True
CLIP/text encoder model load device: cuda:0, offload device: cpu, current: cuda:0, dtype: torch.float16
clip missing: ['text_projection.weight']
@dosubot[bot] commented on GitHub (Sep 26, 2025):
The error
clip missing: ['text_projection.weight']means the CLIP/text encoder model required by your workflow is either incomplete or incompatible. This isn't caused by your ComfyUI Desktop or portable installation, but by the model files themselves.For Flux workflows, you must use the correct combination of models: Flux checkpoints require a specific VAE and two text encoders (CLIP-L and T5-XXL). If you use the wrong CLIP model, or if the file is corrupted or from a different architecture, you'll get missing weight errors like this one.
To fix it:
models/checkpoints/,models/vae/,models/embeddings/).More details and troubleshooting steps are in the official documentation and support threads. This is a common issue when mixing models from different series or using incomplete downloads.
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
@qlxxkj commented on GitHub (Sep 26, 2025):
I switched to flux_dev_fp8 workflow and got the same error. I also changed the Model Loader node to fp8_e4m3fn but it didn't work.
@dosubot[bot] commented on GitHub (Sep 26, 2025):
The persistent
clip missing: ['text_projection.weight']error in fp8 workflows (even after switching to flux_dev_fp8 and setting the Model Loader node to fp8_e4m3fn) means the CLIP/text encoder model file is incomplete, corrupted, or incompatible with the workflow. This is not caused by the workflow or node settings, but by the actual model files being loaded.For fp8 Flux workflows, you need these exact models:
clip_l.safetensorsandt5xxl_fp8_e4m3fn.safetensorsinmodels/text_encoders/ae.safetensorsinmodels/vae/flux1-schnell.safetensorsorflux1-krea-dev_fp8_scaled.safetensors) inmodels/diffusion_models/Make sure you download all model files directly from trusted sources like Hugging Face, and verify their file sizes and hashes if possible. Place them in the correct folders and double-check that your workflow nodes reference the right files. If you still see the error, re-download the models to rule out corruption, and avoid mixing models from different series or using incomplete downloads [docs].
If you use custom nodes, disable them and run only the default workflow with the required models to isolate the issue. More troubleshooting details are in the official documentation and model setup guide.
Let me know if you need direct download links or help verifying your model files.
To reply, just mention @dosu.
Docs are dead. Just use Dosu.
@qlxxkj commented on GitHub (Sep 27, 2025):
The previous version worked normally, it was not a problem with the model
@dosubot[bot] commented on GitHub (Sep 27, 2025):
You're right—the problem isn't with your model files if they worked in the previous version. This kind of regression after an upgrade is usually caused by a mismatch between the ComfyUI Desktop (stable) version and the requirements of advanced workflows like Flux.1 Kontext Dev. The Desktop version often lags behind the Nightly/development branch, missing critical updates or nodes needed for these workflows, which leads to errors like
clip missing: ['text_projection.weight']even when your models are correct [docs].To fix this, update to the latest Nightly version of ComfyUI (not just the Desktop stable build), reset or recreate your virtual environment, and reinstall dependencies. If you use custom nodes, disable them to rule out conflicts. These steps resolve most upgrade-related issues where the environment or dependencies become inconsistent [troubleshooting].
This is a known limitation of the Desktop app—advanced workflows may require features or fixes only available in the Nightly branch [model issues]. For future upgrades, back up your configs and consider tracking Nightly releases if you rely on cutting-edge workflows.
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
@qlxxkj commented on GitHub (Sep 27, 2025):
Where can I download the latest Nightly version? @dosu
@dosubot[bot] commented on GitHub (Sep 27, 2025):
The latest Nightly (development) version of ComfyUI is not available as a Desktop installer. To get Nightly, use either the Portable version (Windows only) or Manual installation:
For Windows Portable: Download the Portable package (see the official Portable guide), then run the update script
update/update_comfyui.batin the extracted folder to switch to the latest Nightly build. This keeps your install up to date with the newest features and fixes details.For Manual install (all platforms): Clone the repo with
then run
in the ComfyUI directory. This always gives you the latest Nightly code manual install steps.
The Desktop app only tracks stable releases, so it may lag behind Nightly and miss critical updates needed for advanced workflows see docs.
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
@qlxxkj commented on GitHub (Sep 27, 2025):
The latest Nightly (development) version of ComfyUI is also have the error. @dosu
Here is logs:
got prompt
Using pytorch attention in VAE
Using pytorch attention in VAE
VAE load device: cuda:0, offload device: cpu, dtype: torch.bfloat16
Requested to load AutoencodingEngine
loaded completely 11011.0 159.87335777282715 True
Using scaled fp8: fp8 matrix mult: False, scale input: False
Requested to load FluxClipModel_
loaded completely 9.5367431640625e+25 4903.231597900391 True
CLIP/text encoder model load device: cuda:0, offload device: cpu, current: cuda:0, dtype: torch.float16
clip missing: ['text_projection.weight']
@dosubot[bot] commented on GitHub (Sep 27, 2025):
The
clip missing: ['text_projection.weight']error means the CLIP/text encoder model loaded by your workflow is missing a required parameter, usually because of a model architecture mismatch or an incorrect model file—even if the same files worked before. For Flux workflows, you must use bothclip_l.safetensorsandt5xxl_fp8_e4m3fn.safetensors(ort5xxl_fp16.safetensors) in the DualCLIP node, with each in its correct slot. If you accidentally load the same model in both slots, or use a model from a different series, you’ll get this error. Double-check your node configuration and model paths, and re-download the models from trusted sources if needed. Also, make sure you’re not mixing models from different architecture families in the same workflow details setup guide.If you’re sure the models and workflow are correct, try disabling all custom nodes and running only the default workflow to rule out conflicts. If the error persists after a Nightly upgrade, it’s likely a configuration or model compatibility issue, not a bug in the ComfyUI core.
To reply, just mention @dosu.
Docs are dead. Just use Dosu.
@webfiltered commented on GitHub (Sep 28, 2025):
@qlxxkj What GPU do you have? You said you updated to CUDA 12.8; was that because you CAN'T update to 12.9? If you're on a 10 series card, you just need to use an older version of pytorch:
@qlxxkj commented on GitHub (Sep 30, 2025):
@webfiltered commented on GitHub (Sep 30, 2025):
I would definitely try one of the commands I suggested. You can run either one from inside Comfy, then restart the app once done. The issue is unlikely to be related your graphics driver.
@qlxxkj commented on GitHub (Oct 9, 2025):
I can't fix it after running either one.
@qlxxkj commented on GitHub (Oct 10, 2025):
How to use pytorch (2.5.1+cu121) in the latest version of ComfyUI desktop? After installing pytorch (2.5.1+cu121) in the comfyui virtual environment, the desktop application still uses pytorch (2.8.0+cu129) when opening it. @webfiltered
@qlxxkj commented on GitHub (Oct 10, 2025):
Each time a workflow is executed and a reconnect occurs, the following Windows system log appears:
System event log: Windows successfully diagnosed a low virtual memory situation. The following programs used the most virtual memory: python.exe (11896) used 25301602304 bytes; ComfyUI.exe (6964) used 358973440 bytes; MsMpEng.exe (4412) used 330895360 bytes.
@qlxxkj commented on GitHub (Oct 10, 2025):
I've fixed this issue. According to the Windows system event log, I found that the "Reconnecting" error was caused by insufficient system memory. Perhaps a workflow execution caused a memory overflow, leading to a memory failure. Reinserting the two 16GB memory sticks fixed the issue. @webfiltered
@dosubot[bot] commented on GitHub (Jan 9, 2026):
Hi, @qlxxkj. I'm Dosu (https://dosu.dev), and I'm helping the desktop team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thanks for your understanding and contribution!