Skip to content
This repository has been archived by the owner on Sep 22, 2022. It is now read-only.

Consider handling Queue Mutex PoisonErrors #2

Open
koenw opened this issue Apr 15, 2022 · 0 comments
Open

Consider handling Queue Mutex PoisonErrors #2

koenw opened this issue Apr 15, 2022 · 0 comments

Comments

@koenw
Copy link
Contributor

koenw commented Apr 15, 2022

These can only occur if the thread holding the lock crashes, which should ofc not happen but if it happens the application would just deadlock for eternity which is not very helpful. Since properly recovering from such an error can be complex and difficult (like making sure the crashed process is really not around anymore) I think even just printing a message that the look has been poisoned and the application is now hanging would already greatly benefit some future person troubleshooting this potential hang.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant