GUI slows down on local network after one generation

[AzraelMilosz]

I added a —listen parameter to the webguiuser file so that I can access the app on my iPad locally while I’m running it from my PC and everything is working fine until I do a generation. Afterward the app slows down and even typing or deleting a single letter can take 10-30 seconds…each!

Any idea why this might be happening? Is there a fix for this?

[Heathen]

It's a problem with Gradio, it passes images as data (more info here) streams instead of links to local files. That, specially for data:image, can be really slow on weaker devices, such an iPad or an android tab/phone.

[AzraelMilosz]

Is there a fix for this? Would it at least better if I made a public link and accessed it through there?

[Heathen]

Well, avoid generating more than one image at a time. Each one is a separate data:image link.

Only other solution I can think of is using any remote control app to use your PC's desktop in your phone. A bit jank to use your PC browser in your phone, but if your device is having trouble with data:image, it might be better that way.

[AzraelMilosz]

That is what I was originally going to do, but I figured this was a better way, and less expensive.

[evanjs]

If it's the same issue as #232, then this should be resolved by gradio-app/gradio#2265

[AzraelMilosz]

It does appear to be the same issue, but I cannot find the folder/files anywhere in the stablediffusion webui. So I have no idea how to delete the h_full.

[evanjs]

This should no longer be required as of 4ed99d5.
The repository now uses a version of Gradio (3.5) that should resolve the issue.

[AzraelMilosz]

Sorry, I’m new to GitHub, am I able to just pull the updated gradio from the automatic1111 repo and not change anything else? I’ve heard some people are having issues with the new version (like img-img not working anymore) so I’m reluctant to just do a pull and update the whole thing.

[evanjs]

You can either change the version listed in requirements_versions.txt

-gradio==3.4.1
+gradio==3.5

Or you can update to the latest version altogether.

Just note that, if you only update the version listed in requirements_versions.txt, you might experience some issues with Gradio 3.5 that have been fixed already.

[evanjs]

Unable to test at the moment, but if I understand correctly, #2924 addresses both sides of the compatibility quirk I mentioned.

The issue with img2img was introduced when we updated to Gradio 3.5.

However, this was due to other bits that fixed things on Gradio 3.4.1.

It seems like the issue has since been fixed, and it should be safe to update.