-
Notifications
You must be signed in to change notification settings - Fork 27.8k
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]: webui fails to start with Torch is not able to use GPU error #8222
Comments
I've just started getting this as well was working yesterday |
I had these extensions too |
Same here. 😌 |
You can get it to start with --skip-torch-cuda-test but it won't produce anything because it can't access cuda |
Started it with --skip-torch-cuda-test and clicked update extensions and got this error:
|
tried using |
trying to update my nvidia drivers as well. Though I suspect one of the extension updates broke it because it worked before I updated dreambooth and controlnet. |
After Dreambooth too. |
I did update and restart on both at once them it failed, I had both extensions working before but both had updates available. |
Disabled all my extensions and tried to start without --skip-torch-cuda-test, but got original error. |
Ive removed recently updated extensions but doesn`t help at all. |
Torch is not able to use GPU basically is the issue we just need to figure out why, I think they must have broken the environment in someway was hoping it might help to reinstall requirements but no luck. |
I've renamed my venv folder and I'm running it again to get it to reinstall the environment itself |
let you know how it goes |
I doubt it's controlnet, I'm suspecting dream booth |
Updated drivers. Pointless. |
Indeed it was but I believe in being through. I notice dreambooth requirements.txt look like it was updated 13 hours ago |
I could start and generate an image with |
renaming or removing venv works as it forces it to rebuild the environment I have it working again now |
But it will redownload all the requirements which takes a little while. |
Noticed it's saying |
It's always dreambooth that seems to break it, I'm removing it for now my Graphics card can't really cope with it anyway and I train on Colab now. |
Installed latest nvidia drivers. Deleted venv directory. Restarted. Now getting this error:
|
Are you getting that error after you do something in the UI? Mines worked fine since I deleted venv and it replaced it it. |
found this |
Not sure why you have this issue and I didn't though |
#7759 fixed the last issue. It's working again as before and now saying |
Controlnet seems about 4 times slower though |
Not for me though. |
…- Windows OS. Might Fix bugs similar to AUTOMATIC1111#8222, where the python subprocess.run does not work properly due to the shell=True parameter. This, in turn, might make webui.bat unfunctional on the Windows platform. Related to any errors of commands that use the return of subprocess.run on launch.py (including webui.bat), such as 'Torch is not able to use GPU; add --skip-torch-cuda-test to COMMANDLINE_ARGS variable to disable this check', and any other errors installing requirements. This fix needs more tests on other versions of Windows before approval. From https://docs.python.org/3/library/subprocess.html: "The only time you need to specify shell=True on Windows is when the command you wish to execute is built into the shell (e.g. dir or copy). You do not need shell=True to run a batch file or console-based executable." Tested on Windows 10.
Is there an existing issue for this?
What happened?
Failed to start webui. Was working this morning, this afternoon this happened. Nothing changed except for git pull from automatic1111 repository and clicked check for updates on extensions.
Steps to reproduce the problem
What should have happened?
Webui should have started as always
Commit where the problem happens
Commit hash: cca6e52
What platforms do you use to access the UI ?
Windows
What browsers do you use to access the UI ?
Mozilla Firefox
Command Line Arguments
List of extensions
controlnet
dreambooth
instruct2pix
Console logs
Additional information
Was working this morning
The text was updated successfully, but these errors were encountered: