stable-diffusion-webui
stable-diffusion-webui copied to clipboard
AUTOMATIC1111
[Bug]: Generate Forever stops working after 1 or more generation batches
Is there an existing issue for this?
- [X] I have searched the existing issues and checked the recent builds/commits
What happened?
The UI's Generate Forever feature stops working after 1 or more generation batches (batch size of 50 stops after 1 batch, while smaller batch sizes take longer to stop working).
Steps to reproduce the problem
Use the generate forever feature and wait.
What should have happened?
It should work indefinitely until the user stops it.
Commit where the problem happens
98947d173e3f1667eba29c904f681047dea9de90
What platforms do you use to access UI ?
Windows, Linux
What browsers do you use to access the UI ?
Mozilla Firefox, Google Chrome
Command Line Arguments
No response
Additional information, context and logs
No response
Can't reproduce this locally, can you please report any errors you see in the browser developer console prior to generate forever failing.
Any idea on the time frame for smaller batch sizes?
This is controlled by a client side 'setInterval' loop of 500 ms, so I'd not expect an error in one call to have any effect on others until the browser window was refreshed or closed.
@dfaker I would try testing with a batch size of 50, as it fails on the second or third batch . I am unable to reproduce the bug at lower batch sizes. There are no errors when it fails. It just stops working, thought it stops working after completing the batch.
And nothing in the terminal window to indicate that there's a failure on the back-end either?
I can't see, at the moment, how the loop that looks for and attempts to click the generate button can fail, not do we have any indication of any other client side or back-end failure, I'm not sure what routes we can progress this on.
@dfaker Nothing to indicate why it happens on the terminal window or the UI page.
It also just happened again while using the DPM++ 2S a Karras sampler after reaching 2750 images using a batch size of 50. It stopped working just after 100% completion of the current batch according to the terminal.
Previously it happened with the DPM++ 2M Karras sampler.
Is the generate button still clickable to manually run a new generation when it's in this stopped state? Are you switching to another tab in the webui when this happens?
@dfaker The generate button no longer works and I have to restart the UI to fix it. And I am not switching to another WebUI tab at all during the rendering.
Okay! that has a different character! The generate button stops working, that's what the generate forever function is trying to automatically click for you.
Just had it happen again when DPM++ 2S a Karras sampler after reaching 2100 images using a batch size of 50 and 50 steps. A simple F5 refresh fixes it, but its problematic as it can fail when I'm not monitoring it's progress.
I haven't had this issue happen with the older sampler before, so it may be related to the new samplers.
Just froze again while using DPM++ 2S a Karras sampler after reaching 400 images using a batch size of 50 and 50 steps. This time it stopped at 86% completion according to the UI, but the terminal shows that it completed the batch.
This sounds more like a communication failure between the front end and the back, if it's not related if the progress is halted and the buttons aren't responding - is this running on your local machine or are you sharing it from the cloud or elsewhere?
same problem, while using "Euler a", 30 steps, batch count 1, batch size 4; after generate, the output area still show last img, can't see the 4 new imgs, but it's acturally in the local folder And the "Generate" button didn't response after click, also solved by refresh the page
This is a very old issue, and a pretty extreme case at that. I also can't reproduce what was mentioned above. Going to close this as stale. If this is somehow still an issue feel free to open a new one.
