-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
image outputs stop working #6
Comments
Commit 5d45c92 now handles image output updating with yield and not refreshing at every 1 sec. This also means that the images stay local to each session. Full multiuser operation is still not supported, as the model is still global. |
The problems still occurs, at least partly same as issue #8 . Currently, diffusion stops at an iteration without error message, GO button does not respond any more and the queue is released (leading to the impression that the operation was captured by another client). Happens very often on iPad, also otherwise it seems not to happen on all devices. Anyhow, using yield did not solve the problem, indicating that the iteration loop gets stuck on the client side. |
I have been able to reproduce the problem using the following test script so as to show it is indeed a gradio issue and will report it to their repo.
|
Filed an issue here gradio-app/gradio#4761 |
Image outputs should be updated every 1 sec, but this stops working seemingly randomly, most likely after the UI has been inactive and then a new generation is started.
This is quite serious as one has all settings and inputs ready, yet cannot see the outputs, and reloading the page will throw all inputs and settings away.
Maybe having every on all the time is a bad idea, and we should create the every handler only when the generation starts? Or alternatively discard the every=1 handler and instead use diffusion_run as a generator yielding images which are then read in a loop and displayed.
It is not obvious however, how gradio handles the browser - server interaction. under the hood.
The text was updated successfully, but these errors were encountered: