Auto Recover From CUDA error #204
Open
+76
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created bat file to re-launch automatic1111 is closed, or completely crashes.
Created setting to enable closing automatic1111 on cuda error
modified task_runner.py to exit when setting is enabled, and automatic1111 log message includes CUDA error.
I though I would share this, incase it's useful to other people.
Using this cuda error recovery method, I can usually run batches in automatic1111 for several days without issue
I tried using automatic's restart method, like automatic uses to install extension updates. But that was found to be ineffective. (didn't recover from cuda error) exiting automatics is effective recovery from cuda error.