-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[BUG] deadlock in process_renderables #1061
Labels
Comments
If I comment "with self._lock:", there is no more deadlock without any other issue |
An other different problem that arise with the program above, is that the average transfert speed disappear from the task once it is finished |
Please try v9.12.1 |
Should be fix. Re-open if you still have a problem. |
thanks, it seems to correct the problem. |
This was referenced Mar 8, 2021
This was referenced Jun 6, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, I encounter a random deadlock in process_renderables, https://github.com/willmcgugan/rich/blob/master/rich/live.py at line 242, it cannot acquire the lock;
To reproduce use this program based on your examples:
$ kill -SIGABRT PID
Trace:
File "/home/localadmin/.local/lib/python3.6/site-packages/rich/live.py", line 242 in process_renderables
File "/home/localadmin/.local/lib/python3.6/site-packages/rich/console.py", line 1402 in print
File "/home/localadmin/.local/lib/python3.6/site-packages/rich/live.py", line 228 in refresh
File "/home/localadmin/.local/lib/python3.6/site-packages/rich/progress.py", line 848 in refresh
File "/home/localadmin/.local/lib/python3.6/site-packages/rich/progress.py", line 935 in add_task
File "./deadlock.py", line 122 in download
File "./deadlock.py", line 134 in main
File "./deadlock.py", line 141 in
Aborted
The text was updated successfully, but these errors were encountered: