[X] I have searched the existing issues and checked the recent builds/commits
What happened?
In the event that a user decides to abort an unfinished image generation process, there is a certain probability that the program will freeze:
After pressing "interrupt", the generation is paused, but the GPU and VRAM remain in a high-utilization state. The console window may display either incomplete or complete status, and there's no error in the log, but at this point, the web interface is frozen, preventing further actions. The only option at this point is to close the backend, keep awaiting is not likely to make difference.
When this situation occurs, likes, when the user presses "Interrupt" and the program freezes, the web interface will not show any further changes apart from the progress suspending. Subsequently, when the user closes the console window, the web interface, will display "Connection errored out" as usual, and the "Interrupt" button will revert back to the "Generate" button.
This bug has been present since early versions, occurred infrequently in recent versions, and resurfaced after 1.6 versions. (this is subject to verification).
Steps to reproduce the problem
Generate an image.
Press "Interrupt" before the generation is finished.
There'll be a slight chance of freezing.
The occurrence probability of this issue is not too high; it may take dozens to hundreds of repetitions to reproduce. In cases of bad luck, the freeze may occur on the first attempt at such an operation.
My guess is that it may be related to the workload, and this issue is more likely to occur in when generating high resolution images, or using i2i mode, or using ControlNet.
It's also not due to setting parameters too high, causing the workload to far exceed the device's capabilities. Instead, it just happens occasionally during normal generations.
What should have happened?
Ideally, the program should not freeze and stop generating immediately after the user has pressed the Interrupt button.
Is there an existing issue for this?
What happened?
In the event that a user decides to abort an unfinished image generation process, there is a certain probability that the program will freeze:
After pressing "interrupt", the generation is paused, but the GPU and VRAM remain in a high-utilization state. The console window may display either incomplete or complete status, and there's no error in the log, but at this point, the web interface is frozen, preventing further actions. The only option at this point is to close the backend, keep awaiting is not likely to make difference.
When this situation occurs, likes, when the user presses "Interrupt" and the program freezes, the web interface will not show any further changes apart from the progress suspending. Subsequently, when the user closes the console window, the web interface, will display "Connection errored out" as usual, and the "Interrupt" button will revert back to the "Generate" button.
This bug has been present since early versions, occurred infrequently in recent versions, and resurfaced after 1.6 versions. (this is subject to verification).
Steps to reproduce the problem
The occurrence probability of this issue is not too high; it may take dozens to hundreds of repetitions to reproduce. In cases of bad luck, the freeze may occur on the first attempt at such an operation.
My guess is that it may be related to the workload, and this issue is more likely to occur in when generating high resolution images, or using i2i mode, or using ControlNet.
It's also not due to setting parameters too high, causing the workload to far exceed the device's capabilities. Instead, it just happens occasionally during normal generations.
What should have happened?
Ideally, the program should not freeze and stop generating immediately after the user has pressed the Interrupt button.
Sysinfo
sysinfo-2023-10-04-16-39.txt
What browsers do you use to access the UI ?
Microsoft Edge
Console logs
Additional information
In the logs above, only the last generation process got stuck. The other unfinished ones are not problematic.