-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
show_image_info: IndexError: list index out of range #34
Comments
@axemaster This latest commit does that. Let me know, if that solves the issue. |
I still got the same error when I browse over an image in the image browser or try to delete an image. |
It didn't. Still the same error. I hope you can solve it! |
I also experience an error: |
|
I probably found it. When I did the previous commit, apparently one file was not uploaded. That's why it worked for me. Can you try the latest commit? |
This error happens everytime after I do a update of the extension and click "Apply and restart UI". The UI is then not really working anymore, everywhere is "error" displayed. I have to restart the UI again, then it works again. |
@Woisek I just ran this through debug. After pressing "Apply and restart UI", those two actions are executed concurrently. So the reload-ui probably still get at leasts parts of the old extension version. Seems like a bug on the webui side to me. |
@AlUlkesh |
It's working again! Just updated it and everything is back to normal. |
Latest commit fixes the issue on my end as well. GJ! |
Latest commit seems to have solved the issue. I'll close this. If anyone still has problems, please make a new issue. |
I am no longer getting the error. But, yes I often kill A1111 and do not refresh browser. (( too much information section )) because doing the latter loses too many values in the UI, and on Mac M1 image generation never releases memory after processing (bug!) so the process gets huge and very slow. It is necessary to kill it often. I wish there was an option for it to release and reload SD after every batch. I think to do this they would need to separate the UI python process and imaging engine process, otherwise they break gradio etc. ¯_(ツ)_/¯ |
@axemaster
The text was updated successfully, but these errors were encountered: