[issue30549] ProcessPoolExecutor hangs forever if the object raises on __getstate__

[Berker Peksag]

Change by Berker Peksag :


--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Deadlocks in `concurrent.futures.ProcessPoolExecutor`

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30549] ProcessPoolExecutor hangs forever if the object raises on __getstate__

[Grzegorz Grzywacz]

Grzegorz Grzywacz added the comment:

This is already reported and patch was proposed. Here: #30006

--
nosy: +grzgrzgrz3

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30549] ProcessPoolExecutor hangs forever if the object raises on __getstate__

[Roberto Martínez]

New submission from Roberto Martínez:

Hi, I detected that a ProcessPoolExecutor hangs if the object fails to 
picklelize.

I attached the simplest code to reproduce the behavior. Note that the 
interpreter should exit after the exception but it doesn't and hangs forever.

I tested with python 3.4, 3.5 and 3.6 with the same results.

--
files: test_noshutdown.py
messages: 294999
nosy: Roberto Martínez
priority: normal
severity: normal
status: open
title: ProcessPoolExecutor hangs forever if the object raises on __getstate__
type: behavior
versions: Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file46919/test_noshutdown.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com