You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Vulkan Memory Allocation Failure on Large Buffer Request (ErrorOutOfDeviceMemory) #734
That's a hard limit of the Vulkan backend, I tried to find a way to work around it, but I'm not sure it's even possible. That being said, I don't think there's any sd1.x model that works well at such high resolution anyways.
@zhou7510 , could you try again with master-309-35843c7 ? It includes many new options for reducing VRAM usage (--vae-conv-direct, --diffusion-conv-direct, --offload-to-cpu). I was able to generate even larger images with less than 4G VRAM.
This issue has had no activity for one year. The latest version of the code may already have fixed the problem.
If the issue still exists in the latest version, you can reopen this issue at any time with updated reproduction details.
Activity
zhouraym commentedon Jul 21, 2025
My vulkaninfo details are as follows:
Is it possible to avoid allocating such a large amount of GPU memory at once?
stduhpf commentedon Jul 21, 2025
That's a hard limit of the Vulkan backend, I tried to find a way to work around it, but I'm not sure it's even possible. That being said, I don't think there's any sd1.x model that works well at such high resolution anyways.
wbruna commentedon Sep 5, 2025
There is a new llama.cpp PR that seems to address this: ggml-org/llama.cpp#15815
Indeed, most already struggle around 768x768. Could be nice for low-strength img2img, though.
Green-Sky commentedon Sep 5, 2025
I actually torture sd1 with 768x1024, and throw out ~half.
wbruna commentedon Sep 27, 2025
@zhou7510 , could you try again with
master-309-35843c7? It includes many new options for reducing VRAM usage (--vae-conv-direct,--diffusion-conv-direct,--offload-to-cpu). I was able to generate even larger images with less than 4G VRAM.github-actions commentedon Sep 28, 2026
This issue has had no activity for one year. The latest version of the code may already have fixed the problem.
If the issue still exists in the latest version, you can reopen this issue at any time with updated reproduction details.