You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Deadlocks in concurrent.futures.ProcessPoolExecutor with pickling error #75880
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2018-01-05.12:33:10.791>created_at=<Date2017-10-05.07:41:45.845>labels= ['3.7', 'type-bug', 'library']
title='Deadlocks in `concurrent.futures.ProcessPoolExecutor` with pickling error'updated_at=<Date2018-01-05.12:33:10.789>user='https://github.com/tomMoral'
When using concurrent.futures.ProcessPoolExecutor with objects that are not picklable or unpicklable, several situations results in a deadlock, with the interpreter freezed.
New changeset 94459fd by Antoine Pitrou (Thomas Moreau) in branch 'master': bpo-31699 Deadlocks in concurrent.futures.ProcessPoolExecutor with pickling error (bpo-3895) 94459fd
Activity
tomMoral commentedon Oct 5, 2017
When using
concurrent.futures.ProcessPoolExecutorwith objects that are not picklable or unpicklable, several situations results in a deadlock, with the interpreter freezed.This is the case for different scenario, for instance these three : https://gist.github.com/tomMoral/cc27a938d669edcf0286c57516942369
The different pickling/unpickling error and their effect should be tested in
test_concurrent_futures.pypitrou commentedon Jan 5, 2018
New changeset 94459fd by Antoine Pitrou (Thomas Moreau) in branch 'master':
bpo-31699 Deadlocks in
concurrent.futures.ProcessPoolExecutorwith pickling error (bpo-3895)94459fd
pitrou commentedon Jan 5, 2018
This non-trivial issue has been fixed now, thanks to Thomas' patch. Thank you Thomas!