generalpenguin89/tpool — Issue #6: BUG: possible deadlock in future_destroy()
Author: generalpenguin89
Created: 2012-01-01 17:33:04+00:00
State: open

If future_destroy() is called when the value is not yet ready, it will return EBUSY without releasing the lock. This means that any subsequent calls to future_get() will block forever regardless of the status of the future value.