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
When generating with many LORAs added, Invoke 4.2.4 reports that my system is out of memory:
It seems to be filling VRAM, but doesn't fall back to system RAM once VRAM is full, then crashes.
I've changed the fallback setting in Nvidia console to system, it makes no difference.
If I use Invoke 4.2.1, it works fine. Unsure about versions in between.
What you expected to happen
Overflowing VRAM should fallback to system RAM, and overflowing system RAM should fallback to Swap. It should not throw an error once VRAM is full.
How to reproduce the problem
Using my setup install Invoke 4.2.1 and generate an image with heavy memory requirements (SDXL, many loras, controlnets, etc). It will work fine.
Then, update to Invoke 4.2.4 and generate another image with the same parameters. It will no longer work and you'll see this error. (use random seed, otherwise it might just copy the last image)
Additional context
My setup is Windows10 > WSL2 > Debian12 > Docker > InvokeAI. This is my docker compose:
Is there an existing issue for this problem?
Operating system
Linux
GPU vendor
Nvidia (CUDA)
GPU model
RTX 2060 Super
GPU VRAM
8GB
Version number
4.2.4
Browser
Waterfox G6.0.16
Python dependencies
No response
What happened
When generating with many LORAs added, Invoke 4.2.4 reports that my system is out of memory:
It seems to be filling VRAM, but doesn't fall back to system RAM once VRAM is full, then crashes.
I've changed the fallback setting in Nvidia console to system, it makes no difference.
If I use Invoke 4.2.1, it works fine. Unsure about versions in between.
What you expected to happen
Overflowing VRAM should fallback to system RAM, and overflowing system RAM should fallback to Swap. It should not throw an error once VRAM is full.
How to reproduce the problem
Using my setup install Invoke 4.2.1 and generate an image with heavy memory requirements (SDXL, many loras, controlnets, etc). It will work fine.
Then, update to Invoke 4.2.4 and generate another image with the same parameters. It will no longer work and you'll see this error. (use random seed, otherwise it might just copy the last image)
Additional context
My setup is Windows10 > WSL2 > Debian12 > Docker > InvokeAI. This is my docker compose:
Discord username
No response
The text was updated successfully, but these errors were encountered: