Open GalenMarek14 opened 11 months ago
I also tried "--no-gradio-queue" but then WebUI didn't even start and gave "ValueError: Progress tracking requires queuing to be enabled." error.
For some reason vladmandic's fork SD.Next works perfectly though (UI-UX doesn't work either)...
Same. I have been having issues with the DOS window showing completion at - for example - 2 minutes 37 seconds, but the UI hanging at 95-97% and a timer going from 5s remaining occasionally increasing more and more, only for the final generation time to be anywhere between 5-8+ minutes.
I tried --no-gradio-queue
but it always errors "progress tracking requires queuing to be enabled." in "...gradio\blocks.py" lines 1690
File "H:\stable-diffusion\stable-diffusion-main\AUTO1111\system\python\lib\site-packages\gradio\blocks.py", line 1690, in validate_queue_settings raise ValueError("Progress tracking requires queuing to be enabled.") ValueError: Progress tracking requires queuing to be enabled. Press any key to continue...
Pressing any key does not continue. :)
I also tried installing UI-UX as a potential workaround but it's not loading either. I have not tried vladmandic's fork. Half the time, generations load super fast, less than 45 seconds for a relatively high resolution. Resource monitoring shows at least 2GB free with no errors. Sometimes I get a websocket disconnect after minutes of wait time before the generation finally finishes less than a second after the error comes up and reconnects.
My custom args are as follows (excluding pathing to ComfyUI checkpoint/embedding/lora folders on the same drive)
--xformers --opt-split-attention --upcast-sampling --medvram --no-half-vae --opt-channelslast
set PYTORCH_CUDA_ALLOC_CONF=garbage_collection_threshold:0.9,max_split_size_mb:512
(this one REALLY helped performance a lot BTW, I wouldn't have to reload everything after just 3-5 gens).
Version version: v1.6.0-2-g4afaaf8a as part of the troubleshooting process, newest as of 11/22/23.
Edit Also, I forgot to mention I ran the gamut of disabling extensions, none of which seemed to make a difference. Also, to clarify, it's not the img2img generate button I'm having issues with, though it does occasionally happen, sometimes it's just a long pause before it does respond.
Is there an existing issue for this?
What happened?
When using resize methods in img2img and clicking generate it shows "waiting" normally but after that is totally random. It sometimes generates the output successfully while sometimes waits and does nothing. Most of the time it doesn't work. All command windows are empty while this happens (I tried normal install and Stability Matrix both cmd and Stability command windows are empty). "--loglevel DEBUG" also shows nothing either. I tried many different browsers (chrome, firefox, edge, brave) but nothing changed. Clearing caches didn't do anything either. Fresh installs without any extensions did nothing also.
I also tried "--no-gradio-queue" but then WebUI didn't even start and gave "ValueError: Progress tracking requires queuing to be enabled." error.
For some reason vladmandic's fork SD.Next works perfectly though (UI-UX doesn't work either)...
Steps to reproduce the problem
What should have happened?
It should have generated a resized image.
Sysinfo
sysinfo-2023-11-13-22-31.txt
What browsers do you use to access the UI ?
Mozilla Firefox, Google Chrome, Brave, Microsoft Edge
Console logs
Additional information
Those logs are taken while the generate button working and after it is 'finished'. Nothing shows.