AUTOMATIC1111 / stable-diffusion-webui-tensorrt

MIT License
310 stars 20 forks source link

I seem to somehow end up stuck in a situation where I cannot generate images at all, it claims no profile can be found, despite me using the same settings that worked moments ago. #75

Open left1000 opened 9 months ago

left1000 commented 9 months ago

I seem to somehow end up stuck in a situation where I cannot generate images at all, it claims no profile can be found, despite me using the same settings that worked moments ago.

I can't figure out how to write useful feedback about this as the error is too generic and simply says no profile found, but then I go and check the list of profiles and it does exist.

The only thread of commonality to when this issue starts is: https://github.com/AUTOMATIC1111/stable-diffusion-webui-tensorrt/issues/74 That is once things freeze duration creation of a profile and I have to close automatic1111's console forcefully, all profiles I have are polluted and can never work again, and require me to delete them all and start over.

This is fairly bad/poor. I almost wonder if model.json is being polluted. In theory it should only be updated when saying a profile, but it must also be edited when clicking to create a profile?

It takes a long time to recreate this error, as I have to create some profiles, test them, see they work, then keep creating more profiles, until I reach the error https://github.com/AUTOMATIC1111/stable-diffusion-webui-tensorrt/issues/74 then I have to try various settings of image generation to ensure none of them will work :(

left1000 commented 9 months ago

Getting the following error https://github.com/AUTOMATIC1111/stable-diffusion-webui-tensorrt/issues/76 seems to have rendered some or all of my profiles unusable, despite having used them successfully moments ago. I'm going to just delete them and rebuild them again for the millionth time. It's strange though as in this case I've been able to use the dynamic 256-512 resolution profile, but using the static 512x768 profile specifically is broken. Again despite having just tested it succesfully moments ago. Not sure what is going on.

But I fear that closing automatic1111 and reopening it is somehow corrupting my rttensor profiles.

left1000 commented 9 months ago

Aaaaaand so much for my theory that closing automatic1111 was breaking profiles. It broke even without being closed. However I did install the wildcards extension and clicked restart ui, and all my static profiles broke. My dynamic one didn't.

Actually my 512x768 and 768x1152 broke entirely but my dynaimc 256-512 square and my 1024x1536 didn't break.

Ideally I'd just pick one of the broken ones and click force rebuild. Easy Peasy. Problem being force rebuild doesn't seem to delete the previous profile. TLDR: a delete button would fix all of these issues and help me narrow down specific bugs isn't of vague unease.

left1000 commented 9 months ago

To clarify, why do I care about the profile continuing to list extra profiles? Well, as of so far, clicking force rebuild and saving a "new" engine profile has never once "worked" as in I keep getting the generic "no profile found" error over and over, no matter how much I try to generate that profile via force rebuild.

Now if I could click delete profile, then build a new profile, I'd narrow down what was wrong. As it is, I have to delete all my profile files, and regenerate all my profiles, if I end up stuck like this.

And I end up stuck like this almost every time the UI for automatic1111webgui reloads or closes and is restarted by me. So, I often have to rebuild all my engines. Which is pretty bad. In theory an option on the extension's GUI that deleted a profile, would potentially fix this issue, and let me regenerate one broken profile, instead of also having to regenerate all the nonbroken profiles.

left1000 commented 9 months ago

Okay so my issues have nothing at all to do with being on the master branch as the dev branch is identical according to my git?

image