-
Notifications
You must be signed in to change notification settings - Fork 82
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
Fatal Python error: PyGILState_Release: auto-releasing thread-state, but no thread-state for this thread #150
Comments
This might be related to the greenlet upgrade that was introduced in Klipper3d/klipper#6525 to allow for the klippy-requirements to be compatible with python 3.12. Which tag of the klipper image are you using?
Could you describe in more detail under which conditions the error is occuring? If possible, please share a full klippy logfile. -Markus |
Hi Markus, thanks for your reply! Regarding your questions: I am using
I have configured an idle timeout to power off my printer after idling for ten minutes:
This turns off a Zigbee plug controlled via Home Assistant effectively turning off the 3D printer (but not the Raspi running Klipper). Most of the time (but not always) after the printer has turned off due to being idle the klipper container terminates with the Python error quoted above. For completeness, I am attaching my The issue happened after the most recent print finished. Please let me know if you need any further details! Thanks, |
I have really no idea whats causing this. Does the crash/restart stop if the printer is turned back on? Could you give |
I deployed your image on Apr 24 and did a couple of prints / power cycles since then. The problem did not manifest again so far, so I am tempted to assume this is related to Python 3.12. |
Thanks for giving it a try. In the light of this issue and also #143, I decided that I will revert the klipper base image back to python 3.11, as it does seem that python 3.12 is a bit too bleeding edge for klipper and I favor reliability over up-to-dateness. For now, at least. To make klipper work on 3.12, the upstream devs would greatly benefit from a description of the issues you encountered, so I'd klindly ask you to reach out to them via their contact points and provide them this valuable information. -Markus |
Hi there,
I am using your
mkuf/klipper
Docker image for my Docker-based Klipper setup on a Raspi 4. Starting with a recent upgrade the container started crashing when my 3D printer becomes idle and powers off. The following error is logged:Has anyone else seen this? Could possibly be related to the Python 3.12 upgrade, but that's just a wild guess...
The text was updated successfully, but these errors were encountered: