Replies: 2 comments 3 replies
-
Anyone have any thoughts on these errors? 2.RecursionError: maximum recursion depth exceeded while calling a Python object The most recent crash just now crashed just 9 minutes into the job. That's the shortest one yet. RecursionError: maximum recursion depth exceeded while calling a Python object Interesting thing is, this is intermittent - if I actually finish a job, I can most likley complete another one if I leave the UI open. But then after some time, it will crash again with one of the errors, using the "maximum recursion" one. |
Beta Was this translation helpful? Give feedback.
-
The first error could be solved by opening helpers/animation.py, go down to the following code: Change the ident of the "if not value_in_number:" to be on the same spacing as the "if value_is_number". Save the file and restart your notebook. Now it should work. About the second error you describe, recursiveness is usually when a function calls itself. The answer in this post has some good information on it and a solution that might work in your case. https://stackoverflow.com/questions/14222416/recursion-in-python-runtimeerror-maximum-recursion-depth-exceeded-while-callin Try changing the recursion limit to 2000 and see if it runs longer. |
Beta Was this translation helpful? Give feedback.
-
I continue to get one of two different errors while running Automatic/3D/Hybrid and am not sure if they are Automatic or Deforum based issues (how to tell?) Both stop the render well short of the final keyframe/maximum frames but at different points if I simply rerun the job. I am using multiple keyframes, but have simplified those down to a single kf, yet the problems persist. Any help would be appreciated.
1 (Deforum extension for auto1111 — version 2.2b | Git commit: ab8650a (Sat Mar 11 10:52:16 2023): UnboundLocalError: local variable 'value_is_number' referenced before assignment
2.RecursionError: maximum recursion depth exceeded while calling a Python object
The most recent crash just now crashed just 9 minutes into the job. That's the shortest one yet.
Not sure if this helps: File "C:\Users\dhaym\AppData\Roaming\Visions of Chaos\Examples\MachineLearning\Text To Image\stable-diffusion-webui\venv\lib\site-packages\torch\cuda_init_.py", line 160, in is_initialized
return _initialized and not _is_in_bad_fork()
RecursionError: maximum recursion depth exceeded while calling a Python object
RecursionError: maximum recursion depth exceeded while calling a Python object
Time taken: 9m 22.17sTorch active/reserved: 8069/9690 MiB, Sys VRAM: 12323/49140 MiB (25.08%)
Interesting thing is, this is intermittent - if I actually finish a job, I can most likley complete another one if I leave the UI open. But then after some time, it will crash again with one of the errors, using the "maximum recursion" one.
Beta Was this translation helpful? Give feedback.
All reactions