ComfyUI interface is not working properly!!!

[Drewhhh]

Your question

I updated the ComfyUI backend, and now when I try to use workflows created by others, the interface freezes, the node connections become chaotic, and refreshing the page doesn't help. However, my dependencies seem to be correct. What could be the issue??? I urgently need a solution!!! Thank you!!

Logs

Other

No response

[DaveGravel]

I’m experiencing a similar issue, and it seems to happen when you have custom nodes that are not registered in the custom node manager. It sounds a bit strange, but with the latest version, any workflow using custom nodes that aren't registered causes the app to freeze when it tries to display the node. It might not be exactly the same issue, but here, it's because of that.

[Drewhhh]

I’m experiencing a similar issue, and it seems to happen when you have custom nodes that are not registered in the custom node manager. It sounds a bit strange, but with the latest version, any workflow using custom nodes that aren't registered causes the app to freeze when it tries to display the node. It might not be exactly the same issue, but here, it's because of that.

Yes, whenever I try to use someone else's workflow, if it contains some nodes that I don't have locally, the interface becomes very laggy once I open ComfyUI. Do you know how to solve this problem please?

[ltdrdata]

Disable all custom nodes and try again. If the issue is gone, you need to narrow it down.

[able2608]

I recently encountered a similar issue in which the graph view freezes when a workflow that was previously working fine started running. Tested both gecko-based and chromium-based browsers (firefox and edge to be exact) and the behaviors are consistent across the two browsers. Other components on the page are not affected (run workflow buttons, the side panel in the new UI, even been able to summon the search node panel and the right click menu in the graph view), just unable to move around, zoom in or out, or interact with the nodes, and the connections are all messed up. Refreshing the page does bring back the graph view, but when the workflow starts again it freezes again. Turned out that the culprit was an outdated version of ComfyUI-Custom-Scripts. To be exact, the Show Text node in the pack. The issue was gone after updating the custom nodes. I speculate that the freeze may be (partly) due to changes made to how textboxes (or other multimedia displays like videos and images, since I used to get some weird "ghost " video load nodes that only displays the preview and cannot be deleted, kind of looks like the floating textbox I get when the graph view freezes) are rendered.

[Drewhhh]

I recently encountered a similar issue in which the graph view freezes when a workflow that was previously working fine started running. Tested both gecko-based and chromium-based browsers (firefox and edge to be exact) and the behaviors are consistent across the two browsers. Other components on the page are not affected (run workflow buttons, the side panel in the new UI, even been able to summon the search node panel and the right click menu in the graph view), just unable to move around, zoom in or out, or interact with the nodes, and the connections are all messed up. Refreshing the page does bring back the graph view, but when the workflow starts again it freezes again. Turned out that the culprit was an outdated version of ComfyUI-Custom-Scripts. To be exact, the Show Text node in the pack. The issue was gone after updating the custom nodes. I speculate that the freeze may be (partly) due to changes made to how textboxes (or other multimedia displays like videos and images, since I used to get some weird "ghost " video load nodes that only displays the preview and cannot be deleted, kind of looks like the floating textbox I get when the graph view freezes) are rendered.

Hello! My issue has been successfully resolved. After investigation, it was found that the freezing of the ComfyUI interface was caused by the "easy-use" node. You might as well try disabling this node to see if it can resolve the current problem. If your issue is also triggered by the "easy-use" node, then reinstalling this node may be an effective solution.

[github-actions[bot]]

This issue is being marked stale because it has not had any activity for 30 days. Reply below within 7 days if your issue still isn't solved, and it will be left open. Otherwise, the issue will be closed automatically.