AI Generated Images

it starts flipping frames between the nodes and a different set of nodes.

Yeah, I don't know what would cause that. I use it in Firefox.

Maybe try opening it in Chromium or a private window to disable addons (if you have your Firefox install set up not to run addons in private windows?)

I'm still suspicious of resource consumption, either RAM or VRAM. I don't see another reason that you'd suddenly smack into problems when running ComfyUI.

I'm currently running ComfyUI and Firefox and some relatively-light other stuff, and I'm at 23GB RAM used (by processes, not disk caching), so I wouldn't expect that you'd be running into trouble on memory unless you've got some other hefty stuff going on. I run it on a 128GB RAM, 128GB paging NVMe machine, so I've got headroom, but I don't think that you'd need more than what you're running if you're generating stuff on the order of what I am.

goes investigating

Hmm. Currently all of my video memory (24GB) is being used, but I'm assuming that that's because Wayland is caching data or something there. I'm pretty sure that I remember having a lot of free VRAM at some point, though maybe that was in X.

considers

Let me kill off ComfyUI and see how much that frees up. Operating on the assumption that nothing immediately re-grabs the memory, that'd presumably give a ballpark for VRAM consumption.

tries

Hmm. That went down to 1GB for non-ComfyUI stuff like Wayland, so ComfyUI was eating all of that.

I don't know. Maybe it caches something.

experiments further

About 17GB (this number and others not excluding the 1GB for other stuff) while running, down to 15GB after the pass is complete. That was for a 1280x720 image, and I was loading the SwinIR upscaler; while not used, it might be resident in VRAM.

goes to set up a workflow without the upscaler to generate a 512x512 image

Hmm. 21GB while running. I'd guess that ComfyUI might be doing something to try to make use of all free VRAM, like, do more parallel processing.

Lemme try with a Stable Diffusion-based model (Realmixxl) instead of the Flux-based Newreality.

tries

About 10GB. Hmm.

kagis

https://old.reddit.com/r/comfyui/comments/1adhqgy/how_to_run_comfyui_with_mid_vram/

It sounds like ComfyUI also supports the --midvram and --lowvram flags, but that it's supposed to automatically select something reasonable based on your system. I dunno, haven't played with that myself.

tries --lowvram

I peak at about 14GB for ComfyUI at 512x512, was 13GB for most of generation.

tries 1280x720

Up to 15.7GB, down to 13.9GB after generation. No upscaling, just Newreality.

Hmm. So, based on that testing, I wouldn't be incredibly surprised if you might be exhausting your VRAM if you're running Flux on a GPU with 12GB. I'm guessing that it might be running dry on cards below 16GB (keeping in mind that it looks like other stuff is consuming about 1GB for me). I don't think I have a way to simulate running the card with less VRAM than it physically has to see what happens.

Keep in mind that I have no idea what kind of memory management is going on here. It could be that pytorch purges stuff if it's running low and doesn't actually need that much, so these numbers are too conservative. Or it could be that you really do need that much.

Here's a workflow (it generates a landscape painting, something I did a while back) using a Stable Diffusion XL-based model, Realmixxl (note: model and webpage includes NSFW content), which ran with what looked like maximum VRAM usage of about 10GB on my system using the attached workflow prompt/settings. You don't have to use Realmixxl, if you have another model, should be able to just choose that other one. But maybe try running it, see if those problems go away? Because if that works without issues, that'd make me suspicious that you're running dry on VRAM.

EDIT: Keep in mind that I'm not an expert on resource consumption on this, haven't read material about what requirements are, and there may be good material out there covering it. This is my ad-hoc, five-minutes-or-so-of testing; my own solution was mostly to just throw hardware at the problem, so I haven't spent a lot of time optimizing workflows for VRAM consumption.

EDIT2: Some of the systems (Automatic1111 I know, dunno about ComfyUI) are also capable, IIRC, of running at reduced precision, which can reduce VRAM usage on some GPUs (though it will affect the output slightly, won't perfectly reproduce a workflow), so I'm not saying that the numbers I give are hard lower limits; might be possible to configure a system to operate with less VRAM in some other ways. Like I said, I haven't spent a lot of time trying to drive down ComfyUI VRAM usage.