It's likely that this is a bug in the threadpool implementation - I suggest you 
file an issue in the main repository.

Reply via email to