14 Comments
User's avatar
Alexis ROLLAND's avatar

Thank you for sharing these details and giving us visibility on the improvements made to ComfyUI under the hood. These low level optimizations help to sediment ComfyUI as a real production-grade tool.

Jason Pinaster's avatar

Thank you for your constant improvement.

BUT Unhappily, it is likely fiddling with the programming at a basic level, especially when it affects different systems differently which leads to ComfyUI suddenly stopping running altogether.

This sudden type of crash is reported over and over at the ComfyUI org forum. And it has now affected me with a multi-factor bird's next of interwoven string to unravel.

If you are going to keep doing these "Improvements" please make their unintended side effects more easy to fix.

Jedrzej Kosinski's avatar

I dont think the changes here are related to that at all, could you link the issue reports? i will forward it to the team!

Jason Pinaster's avatar

This is what I posted:

ComfyUI Desktop stopped working on my Windows 11 machine after today’s update. I deleted and tried a re-install but it won’t work. Expletives and hair-pulling deleted.

I have the following error messages:

Base path invalid or unsafe

Reinstall ComfyUI

Install python packages

uv executable

uv cache

Reset virtual environment

Regrettably the Console Logs are blank.

Is there a simple solution?

If not, what’s the complicated solution? Or do I now have a 7K paperweight sitting on my desk?

If you go to the ComfyUI forum, you will see similar posts on a regular basis, ComfyUI just stopping running after updates. If it was one problem, or if each of these problems had an easy fix, it wouldn't be so bad. But I can't help but think that solving one problem will make others worse.

Jedrzej Kosinski's avatar

Gotcha, thank you for the info! The base path error you are experiencing seems to be a Desktop app-only issue - while we look into that, the portable (https://github.com/Comfy-Org/ComfyUI/releases/tag/v0.8.2) or manual install of ComfyUI should work, as those versions of ComfyUI don't have any code that tries to validate base path.

If you have a Discord, could you join our server at https://discord.com/invite/comfyorg, and message me there? Or you can send me a DM, I am Kosinkadink.

Jason Pinaster's avatar

Thanks for the nudge to join ComfyUI on Discord.

I don't seem to have the ability to DM on the channel? Or am I doing it wrong? I'm only marginal on Discord. I'm jasonp9090 on Discord.

Or should I post my problem under Help?

BTW: Is this a viable general solution: https://www.reddit.com/r/comfyui/comments/1q3k5q6/how_to_solve_everything_forever_broken/ ?

Eivind Rebnord's avatar

This is great work - thank you! These optimizations and updates are necessary for keeping ComfyUI at the cutting edge. I had to update to CUDA 13.0 for these optimizations to take effect on my windows desktop, and now my RTX5090 is having a blast. Keep these posts coming.

yoncah's avatar

is this all included simply by upgrading comfy ? thanks

Jason Pinaster's avatar

Comfy crashed again and it looks like I'll have to do another clean install.

The troubleshooting function appears to have a fundamental flaw: You have to fix everything at once (which it won't let you do) instead of being able to work through each solution in sequence....

879's avatar

This update has fixed the errors in the previous version!

Pavel's avatar

Also, even with developer mode enabled, there is no longer a function to save JSON for sending an API. Either bring back the "save as..." option in the menu, or tell me how to retrieve this json. Currently, I am retrieving it through the web browser's terminal in the "network" section.

Pavel's avatar

After the update, everything broke. I'm using a Nvidia Tesla V100. How can I fix it?

CLIPTextEncode

CUDA error: no kernel image is available for execution on the device

Search for `cudaErrorNoKernelImageForDevice' in https://docs.nvidia.com/cuda/cuda-runtime-api/group__CUDART__TYPES.html for more information.

CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.

For debugging consider passing CUDA_LAUNCH_BLOCKING=1

Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

Heiko Hesse's avatar

The last update has crippled my Comfyui Desktop; it can't be started - again - I'm really fed up with this nonsense; I don't want to have to set everything up again every two weeks.

John Dalzell's avatar

I noticed ComfyUI does affect, disrupt my bluetooth audio (nightly on laptop).