-
-
Notifications
You must be signed in to change notification settings - Fork 454
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
[Issue]: Unable to disable flux tools scripts without restarting the server #3715
Comments
valid issue, but... |
Maybe the script should also switch the active model in the dropdown list, so reverting to .dev can be done without loading another intermediate model. And if you try to switch to dev, you will notice it will load it (unless it crashes out of VRAM), but it definitely crashes out of VRAM when you try to generate an image. So it's not just a straightforward switching of models (which I would understand and comply with), but a rather elaborate switching through a third proxy, then a restart of the server to make it work. I can provide logs documenting the above, if it helps. |
yes, ideally it should - but with gradio that is pretty much impossible without massive hacks.
not really. |
How about adding a "force switch model" in the system page where the user can specify which model they want to load, regardless of which model is loaded? I would assume the scripting behind the button would be more flexible than the limitations of the gradio drop-down list. Or a "load specific model" button, so the user can first "unload" (which exists), then "load" (not re-load, but load specifically a model). Just a though, I am unaware both of gradio limitations, and python capabilities. |
what happens if you press unload -> reload? |
It reloads depth / canny, because that is what is written in config.json as the current model |
all-in-all, valid issue. given how little i value depth/canny models from sai as standalone models, this will be on a backlog. |
Issue Description
Basically Flux canny or depth models remain loaded, disabling the scripts does not revert to Flux dev. However the dropdown models lists dev as active. Reverting to dev requires loading another model, then reloading Flux dev, which eventually cascades into a CUDA VRAM error, requiring the restart of the server.
Version Platform Description
07:09:37-332767 INFO Python: version=3.11.9 platform=Windows bin="C:\ai\automatic\venv\Scripts\python.exe"
venv="C:\ai\automatic\venv"
07:09:37-569321 INFO Version: app=sd.next updated=2025-01-16 hash=e22d0789 branch=master
url=https://github.com/vladmandic/automatic/tree/master ui=main
07:09:38-234406 INFO Platform: arch=AMD64 cpu=Intel64 Family 6 Model 165 Stepping 5, GenuineIntel system=Windows
release=Windows-10-10.0.26100-SP0 python=3.11.9 docker=False
07:09:38-237174 DEBUG Packages: venv=venv site=['venv', 'venv\Lib\site-packages']
Relevant log output
Backend
Diffusers
UI
Standard
Branch
Master
Model
FLUX.1
Acknowledgements
The text was updated successfully, but these errors were encountered: