mirror of
https://github.com/Comfy-Org/desktop.git
synced 2026-11-04 23:47:43 +00:00
[GH-ISSUE #1443] [Bug]: black screen after 3-5 generated wan2.2 clips after last update from 0.5.5 to 0.5.8. #414
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#414
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 @MaxFrei91 on GitHub (Nov 24, 2025).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1443
App Version
At least show what you change at dependencies.
Expected Behavior
Actual Behavior
Steps to Reproduce
Debug Logs
Browser Logs
Settings JSON
Other
┆Issue is synchronized with this Notion page by Unito
@MaxFrei91 commented on GitHub (Nov 24, 2025):
With same venv I did reinstall to 0.5.5 - same thing (black screen on my wf). So, it's something on your dependencies and I was too stupid that saved venv after update, not trying to generate something, for a 10 times at least, lol. More you live - more you know.
Alright, from what I saw, it works fine on default comfy nodes. Maybe it doesn't like my custom MoE ksampler somewhy, after 2-3 generations, or it doesn't like how I forcefully clear vram and ram with some custom nodes.
That's all - first impressions, when I chill off - I'll start to find solution for my build (or just use yours after a little work), don't think I'm rude or else, devs did a great job to create desktop one button install comfy, it's I am lazy as cuck, even lazy to speak english, but forcing myself don't use translators.
While wrote this - clean comfy wf (with some additions, ofcourse:)) works fine. Seems to be - it will be a long road to did it great again.
@dosubot[bot] commented on GitHub (Nov 24, 2025):
Hi @MaxFrei91! I'm Dosu and I’m helping the desktop team.
Your experience matches what others have seen when custom nodes or aggressive memory management are involved—these can cause black screens or UI freezes, especially after updates or several generations. The main app and default nodes usually work fine, so the issue is likely with custom nodes or how dependencies are handled in your environment.
The most effective troubleshooting steps are: disable all custom nodes, delete and recreate your
.venvto reset dependencies, clear config files, and checkmain.logandcomfyui.logfor errors about node imports or memory issues. If the problem disappears with default nodes, try adding your custom nodes back one at a time (binary search helps) to isolate the culprit. Updating or replacing problematic nodes, or changing your workflow structure, can sometimes resolve backend hangs or memory errors. If you’re force-clearing VRAM/RAM, make sure your custom nodes aren’t using deprecated APIs or unsupported memory calls—these can cause instability after a few runs reference.If you want to dig deeper, you can share log snippets here and I can help interpret them. Running your workflow in a clean environment or on another machine can also help rule out system-specific issues. Official docs on troubleshooting custom node problems are here: custom node troubleshooting.
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
@MaxFrei91 commented on GitHub (Nov 24, 2025):
@dosu yeah, thank you, Dosubot.
@dosubot[bot] commented on GitHub (Nov 24, 2025):
You're welcome! If you run into more issues or have questions down the road, just let me know—I'm here to help.
To reply, just mention @dosu.
Docs are dead. Just use Dosu.
@MaxFrei91 commented on GitHub (Nov 24, 2025):
@dosu you don't know me well, I can speak with bots for a days, cause I have no life, so stop answering me, or they ban me.
@dosubot[bot] commented on GitHub (Nov 24, 2025):
Understood—I'll pause here. If you ever want to chat again or need help, just ping me!
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
@benceruleanlu commented on GitHub (Dec 1, 2025):
Unsure if this is a desktop specific issue, but there isn't a lot of information to go off on here. Sharing logs could help, will close for now.