You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear,
Congrats on a such polished and well intended piece of software.
I've been testing SimplyPrint and I've discovered that from time to time SimplyPrint and Octoprint get unresponsive. The UI works but commands don't. Checking the logs I see several "can't start new thread" messages. I've noticed that this issue only happens when the printer is turned off for a while (about a night, for example). When I disabled SimplyPrint plugin in Octoprint, the issue was totally gone.
It seems like python threads that check printer connectivity are being created in an uncontrolled way and they aren't being properly finalized, depleting the stock of available python threads in the system.
So is there a setting to avoid this checking?
The text was updated successfully, but these errors were encountered:
Dear,
Congrats on a such polished and well intended piece of software.
I've been testing SimplyPrint and I've discovered that from time to time SimplyPrint and Octoprint get unresponsive. The UI works but commands don't. Checking the logs I see several "can't start new thread" messages. I've noticed that this issue only happens when the printer is turned off for a while (about a night, for example). When I disabled SimplyPrint plugin in Octoprint, the issue was totally gone.
It seems like python threads that check printer connectivity are being created in an uncontrolled way and they aren't being properly finalized, depleting the stock of available python threads in the system.
So is there a setting to avoid this checking?
The text was updated successfully, but these errors were encountered: