-
Notifications
You must be signed in to change notification settings - Fork 1k
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
stuck when call startprint multiple times #1124
Comments
Do you call printcore.connect(...) before startprint? It is called implicitly if you pass port and baud rate to constructor. |
Hi volconst |
From my several trial the clear variable is not need to set false when start print. If this values passed at the beginning "print thread" then will be stuck forever. Somehow at several time run this variable value not passed at begining "print thread" this is the mostly current happen in printcore code |
Do you use serial connection or tcp sockets? |
Serial connection |
@SokobanRyu , I started a review in #1125 |
@volconst |
How long are your print jobs and how often do you invoke them? |
hi printrun developer,
i found some issue on printcore
when i call startprint on printcore the thread is stuck on _sendnext
after investigate this i found this will be stuck after call several(many) times and always stuck
because this variable self.clear sometime set False and command is not sent
note: i run python not using cython only plain python 3.7
the question is why this self.clear set to be False on start print?
thanks,
The text was updated successfully, but these errors were encountered: