Author advance512
Recipients advance512
Date 2014-12-14.23:03:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1418598191.99.0.544871839796.issue23051@psf.upfronthosting.co.za>
In-reply-to
Content
The patches I attached do 2 things:

1. A deadlock is prevented, wherein the main thread waits forever for the Pool thread/s to finish their execution, while they wait for instructions to terminate from the _task_handler thread which has died. Instead, the exception are caught and handled and termination of the pool execution is performed.
2. The exception that was raised is caught and passed to the main thread, and is re-thrown in the context of the main thread - hence the user catch it and handle it, or - at the very least - be aware of the issue.

I tested the patch to the best of my abilities, and am almost certain nothing was changed performance wise nor anything broken. 

Further eyes would, of course, only help for confirming this.
History
Date User Action Args
2014-12-14 23:03:12advance512setrecipients: + advance512
2014-12-14 23:03:11advance512setmessageid: <1418598191.99.0.544871839796.issue23051@psf.upfronthosting.co.za>
2014-12-14 23:03:11advance512linkissue23051 messages
2014-12-14 23:03:11advance512create