mirror of
https://github.com/Comfy-Org/comfy-aimdo.git
synced 2026-11-04 23:37:21 +00:00
[GH-ISSUE #49] RuntimeError: VRAM reservation failed #18
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/comfy-aimdo#18
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 @jovan2009 on GitHub (May 12, 2026).
Original GitHub issue: https://github.com/Comfy-Org/comfy-aimdo/issues/49
Second run of a Wan 2.2 I2V workflow ends in error during low noise ksampler. This is behavior is new to me, I would say it started today with version
comfy-aimdover. 0.4.0. Not many other things has changed (except I did a git pull on ComfyUI today and I updated the nvidia driver to latest but this error started to happen before the driver update).If I want to be precise the second run (that fails) is not an identical workflow with the first run, it is different by having one extra Lora in each chain (3 loras instead of 2). If I restore the Lora configuration back (2 Lora on High, 2 Lora on Low) the error doesn't happen.
@jovan2009 commented on GitHub (May 12, 2026):
Shuffling things around I came to the conclusion that the error happens only in a narrow set of 3 conditions
--fastoptions (FP16 accumulation + fp8_matrix_mult + cublas_ops)If I eliminate/change any of those 3 the error doesn't happen. For example if load the Lora's through standard ComfyUI nodes everything is alright.
I imagine it's impossible to reproduce this because on top of using custom nodes all the safetensors involved are made by me one way or the other (Wan 2.2 nvfp4 quantizations, fp8 quantized text encoder, extracted Lora's from distilled models).
@jovan2009 commented on GitHub (May 16, 2026):
Things got worse (with version
0.4.1) before they got better (with version0.4.2). With version0.4.1I would get errors every time if I used NVFP4 safetensors in the workflow (as soon I replaced them with their FP16 versions errors disappeared). But with version0.4.2everything seems alright now. The issue that I had apparently was fixed before I could update this thread with the errors I had with0.4.1. I think I will close now, thanks a lot!