Comfy-Org / Comfy-Org/ComfyUI

Clearing V-ram when pressing "cancel" button.

Open
#5,762 1 comment 0 reactions 0 assignees View on GitHub
Feature
Dominant language
Python
Stars
133k
Forks
15.7k
Avg merge
1d 7h
Merged PRs (30d)
158

Description

### Feature Idea

Hi.

I just remark that if I press the "cancel" button, and press again "Queue", the v-ram is not cleared.
I used the nodes "ComfyUI_Searge_LLM" (https://github.com/SeargeDP/ComfyUI_Searge_LLM) and when running automatically (queue prompt => auto queue) this run smoothly. But if I press the cancel button, the next prompt have to load again the LLM model which take a lot of time. In fact it occupy more than my 8Gb vram in this case.
I'm running in a RTX 3060 Ti with 8Gb of vram and my processor is an i7-11700 with 32Gb of ram.
I have an extension (don't know which one, could be "tinyterraNodes but not sure) which add a button "Clean up of VRAM usage", and when I press this button after to stop (canceled) the generation, the need of reloading the model is not present and it works like if I didn't press the "cancel" button.

That mean, I believe, there is an action which is done in "normal" (not canceled) run which clear the vram, which is not done when the generation is canceled.

To be clear, here is a resume of the situation :
- When running in batch (auto-queue), no problem.
- When I cancel a generation, the next image take a lot of time to render.
- If I use the extension (maybe it's "tinyterraNodes") to clear the vram after have canceled the generation and before running a new one, this is perfect (as if I didn't push the "cancel" button).

I just don't want to have to stop the "auto-queue", have to press the "clear vram" and launch again.

Thanks in advance !!

### Existing Solutions

Seems to have an option in the "tinyterraNodes" which is doing this very well (but manually).

### Other

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.