Open younyokel opened 1 year ago
I have confirmed this issue on a different setup. I have also confirmed that disabling Batch cond/uncond fixes this. I tested this on the most recent Dev commit/version of v1.6.0-209-g7d60076b
This could be related to #12227 . Given that seems to be the only PR that touched the hijacking mechanics for Inpainting Models. Someone should test this in v1.5.x with the --always-batch-cond-uncond flag passed on start up, as this wasn't enabled by default in previous versions of WebUI. And as such, this could be a problem which has existed for a significant period of time, and just hasn't been caught until now due to the option not being on by default.
Given past Bug reports, this is definitely not confined to just Batch Cond/uncond. See: #10802
Basically to workaround this issue, you can do either of the following: either set NGMS to zero, or disable batch cond/uncond
@w-e-w @AUTOMATIC1111 Given the breaking nature of this issue, could one of you two take a closer look at this? This seems to have been an issue since NGMS was introduced, but wasn't really ever discovered since Batch cond/uncond was turned off by default until v1.6.0. It's possible the issue was introduced with #9177 but no one ever noticed.
Basically to workaround this issue, you can do either of the following: either set NGMS to zero, or disable batch cond/uncond
Seems like it, thanks for pointing it out.
Is there an existing issue for this?
What happened?
The optimization setting called Batch cond/uncond makes inpainting unusable.
Steps to reproduce the problem
What should have happened?
inpaint
Sysinfo
sysinfo-2023-09-24-22-29.txt
What browsers do you use to access the UI ?
Microsoft Edge
Console logs
Additional information
No response