High Vram usage and UI issues #58
Comments
Regarding the high vram usage, you can enable Gradio is unstable for an unknown reason. It will take some time to figure out |
Yeah the ui thing is really weird, some days I get 0 issues, today it gets stuck on every normal generation. |
Apologies if I didn't respond quickly, but I noticed this isn't a isolated incident. I tested another colab and it had the same issues as this one, assuming that other colabs are the same that means this is something from either AUTOMATIC1111's github or gradio itself. |
I have tested this myself and verified that it is a universal issue. Gradio is currently experiencing extremely high demand which causes some network issues. Automatic's repo doesn't handle these errors well which is why it gets stuck.
This seems to be caused new code in Automatic's repo. Difficult to fix from my end but it'll check it out |
The high Vram usage isn't nearly problematic now but it still peaks at the orange peaks. For now, it seems like the only issue here is the high Vram one. |
The High Vram usage I have been experiencing never really happen and the UI issues didn't bother me, until recently. I did the same thing and yesterday it worked but now something is off.
The unusual high vram usage I am seeing when it starts to generate and while it's generating too.
(The orange peak happened when it was done generating and decoded the images)
I know it didn't peak like this, before I screenshotted the image I did my normal AI generating and it peaked on the RED (which means it used almost all of the Vram).
And the UI is broken too, it stops halfway when I was generating it and it always happens if I used the High res fix.
The High Vram usage might be the model or the server or even colab but the UI one is really annoying.
The text was updated successfully, but these errors were encountered: