lllyasviel / lllyasviel/stable-diffusion-webui-forge
[Bug]: Interrupt and Skip Unresponsive
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
### Checklist
- [x] The issue exists after disabling all extensions
- [ ] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [x] The issue exists in the current version of the webui
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet
### What happened?
Using the `Interrupt` or `Skip` button when generating an image does not function or functions with an extreme delay.
Sometimes I want to interrupt a generation if set a resolution too high and it ends up needing very long to generate. It is usually faster just to `Ctrl+C` the terminal and restart than to wait for the interrupt button to work.
In ComfyUI, this happens almost instantaneously or with minimal delay.
### Steps to reproduce the problem
1. Generate an image.
2. Press either `Interrupt` or `Skip`.
3. Wait an eternity for nothing to happen.
### What should have happened?
When pressing `Interrupt` or `Skip`, current generation should stop quickly like in ComfyUI.
### What browsers do you use to access the UI ?
Brave
### Sysinfo
N/A
### Console logs
```Shell
N/A
```
### Additional information
_No response_
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the problem by starting an image generation and pressing the Interrupt or Skip button, then trace those controls through the generation cancellation path. Compare the delay with the expected near-immediate stop; done means both actions reliably stop or skip the current generation promptly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100