You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Gradio gets stuck in loop after clicking an image or button #115
Gradio gets stuck in an infinite loop after clicking on an image or when clicking a button on the panel. The image disappears immediately when doing so.
CPU and GPU activity sticks at only ~5% (10% tops) with Gradio running. So although it's continually loading not much effort seems to be put into it.
Does anyone know what's wrong or how to solve this?
The setup I'm currently using:
Windows 10
Visual Studio 2019 (Community)
Miniconda3
NVIDIA GeForce GTX 1080
CUDA Toolkit v11.7 (installed separately from Miniconda3)
I was wondering if you have solved the problem now?
No, I haven't had a response back from the Huggingface forum and I personally don't know how to fix it. If I know a solution, I'll post it here.
For you can have a try in the installation environment/site_packages gradio/themes/utils/fonts. Py commented in this web site, https://fonts.googleapis.com/, and then remove the browser's cache to try. I tried it and found that it could run.
Activity
Zeqiang-Lai commentedon Aug 29, 2023
The latest code works on my computer. Your issue might be caused by the network connection issues of huggingface gradio.
Jallisto commentedon Aug 29, 2023
Thanks for the suggestion!
I'll see if someone at Hugginface / Gradio knows what's wrong.
mindy0-0 commentedon Aug 31, 2023
I was wondering if you have solved the problem now?
Jallisto commentedon Sep 11, 2023
No, I haven't had a response back from the Huggingface forum and I personally don't know how to fix it.
If I know a solution, I'll post it here.
mindy0-0 commentedon Sep 11, 2023
For you can have a try in the installation environment/site_packages gradio/themes/utils/fonts. Py commented in this web site, https://fonts.googleapis.com/, and then remove the browser's cache to try. I tried it and found that it could run.
MADM1k33 commentedon Mar 12, 2024
Still not fixed