-
Notifications
You must be signed in to change notification settings - Fork 61
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
[Bug]: UI Crashes When Refreshing Lora List #190
Comments
can you remove some Loras from your directory and test the acceptable amount of processing them? also when you have an issue it is a good start to disable all extensions to discard any conflict with other extensions |
can you test with the latest commit? |
fixed check last commit |
Is there an existing issue for this?
What happened?
After updating to the new version (Auto 1.6), I opened the Lora tab on the right. Since no Lora were displayed, I then clicked the refresh icon. This caused the entire page to freeze and eventually show this error:
I've repeated this process four times, and refreshing the Lora tab has consistently caused this crash. Since I have a lot of Loras, it seems like it's struggling to load them all at once, though I never had this issue with the previous version, or any other SD UI.
Refreshing the page caused the UI to restart and then immediately freeze and crash again. So the terminal needed to be closed in order to restart the session.
It's worth mentioning that the embeddings tab also lagged, despite me only having a dozen or so in total. So whatever method is used to load Embeddings / Loras seems to be more demanding and slower than previously. In the old version, I would simply open the Lora tab and every Lora would be listed immediately with its name and thumbnail.
Steps to reproduce the problem
What should have happened?
The Refresh icon should have shown all Lora without issue.
Sysinfo
sysinfo-2023-11-01-02-39.txt
What browsers do you use to access the UI ?
Google Chrome
Console logs
Additional information
On an unrelated note, thank you for the new update! I'm looking forward to exploring it in more depth once this is resolved.
The text was updated successfully, but these errors were encountered: