lllyasviel / lllyasviel/stable-diffusion-webui-forge

Gradio errors and warnings

Open
#1,185 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
13k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

Hi there, first of all thanks for all the hard work, I love forge <3

Since the upgrade to Gradio 4 there is starting to pop up a lot of warnings and errors in the browser console and I believe they are the reason the gui can become very slow sometimes, this is with a completely fresh forge install and in incognito mode, it happens for both chrome and edge. If you install extensions ( https://github.com/BlafKing/sd-civitai-browser-plus is a good example) it causes even more warnings and the gui becomes more unresponsive.
![image](https://github.com/user-attachments/assets/1895effb-e745-47c7-8472-4c25544321c1)

When you generate an image you get this:
![image](https://github.com/user-attachments/assets/6802e92f-ef78-4411-baa2-a7fb27d7b314)

It seems that its a known problem for gradio so im not sure if its just on their end. But my guess is it might be something in .\webui\script.js
https://github.com/gradio-app/gradio/issues/7726
https://github.com/gradio-app/gradio/pull/7107
https://github.com/gradio-app/gradio/issues/8256

Once again, thanks for all the work <3 <3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the browser-console warnings and errors in a fresh Forge install, both during normal use and image generation, then inspect .\webui\script.js alongside the linked Gradio issues and pull request. Done means the cause is identified and the relevant console errors and resulting GUI slowdown are addressed, or the issue is shown to be entirely upstream.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, python
Domain
frontend, performance, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.