-
Notifications
You must be signed in to change notification settings - Fork 191
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]: CLIP Interrogation crashes #10
Comments
Workaround btw is adding "--use-cpu interrogate" to the cmdline args for anyone having the same issue |
I added a fall back to cpu. |
|
There is a same issue on DirectML repo, it was a problem of pytorch. |
Any work around for this that we can do on our end for now? Kinda sucks not being able to interrogate 😆 |
Just what I've already mentioned above: "tagger" extension |
Is there an existing issue for this?
What happened?
Tried interrogating an Image in img2img with CLIP, but got this crash and in the prompts box.
Since my GPU is neither CUDA nor HIP due to being on Win11, this crash happens. Maybe put CPU as a Fallback Default?
Steps to reproduce the problem
What should have happened?
CLIP Output in Prompt, no Crash in Console.
Commit where the problem happens
c888249
What platforms do you use to access the UI ?
Windows
What browsers do you use to access the UI ?
Google Chrome
Command Line Arguments
List of extensions
Console logs
Additional information
CPU: 5950x
RAM: 32GB
GPU: 7900 XTX
VRAM: 24GB
The text was updated successfully, but these errors were encountered: