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
Invoke will occassionally get stuck at "Generating Running VAE Decoder" when attempting to generate. GPU-load will go to 100% when this happens and I need to restart Invoke to break out of it.
This started occuring immediately after upgrading from 5.5.0 to 5.6.0. So far it feels like this only happens after changing model/checkpoint although I haven't confirmed this.
What you expected to happen
For generating to work without getting stuck
How to reproduce the problem
No confirmed steps to reproduce, although it feels like frequent model/checkpoint changes increases the likelihood of problem occuring
Additional context
No response
Discord username
No response
The text was updated successfully, but these errors were encountered:
adoermenen
changed the title
[bug]: Gets stuck at "Generating Running VAE Decoder"
[bug]: Gets randomly stuck at "Generating Running VAE Decoder"
Jan 25, 2025
Is there an existing issue for this problem?
Operating system
Windows
GPU vendor
Nvidia (CUDA)
GPU model
RTX 4090
GPU VRAM
24GB
Version number
5.6.0
Browser
Microsoft Edge 131.0.2903.146
Python dependencies
accelerate 1.0.1
compel 2.0.2
cuda 12.4
diffusers 0.31.0
numpy 1.26.3
opencv 4.9.0.80
onnx 1.16.1
pillow 10.2.0
python 3.11.11
torch 2.4.1+cu124
torchvision 0.19.1+cu124
transformers 4.46.3
xformers Not Installed
What happened
Invoke will occassionally get stuck at "Generating Running VAE Decoder" when attempting to generate. GPU-load will go to 100% when this happens and I need to restart Invoke to break out of it.
This started occuring immediately after upgrading from 5.5.0 to 5.6.0. So far it feels like this only happens after changing model/checkpoint although I haven't confirmed this.
What you expected to happen
For generating to work without getting stuck
How to reproduce the problem
No confirmed steps to reproduce, although it feels like frequent model/checkpoint changes increases the likelihood of problem occuring
Additional context
No response
Discord username
No response
The text was updated successfully, but these errors were encountered: