Issue 30549: ProcessPoolExecutor hangs forever if the object raises on getstate (original) (raw)
Issue30549
Created on 2017-06-02 09:15 by Roberto Martínez, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Files | |||
|---|---|---|---|
| File name | Uploaded | Description | Edit |
| test_noshutdown.py | Roberto Martínez,2017-06-02 09:15 |
| Messages (2) | ||
|---|---|---|
| msg294999 - (view) | Author: Roberto Martínez (Roberto Martínez) | Date: 2017-06-02 09:15 |
| 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. | ||
| msg296577 - (view) | Author: Grzegorz Grzywacz (grzgrzgrz3) * | Date: 2017-06-21 19:56 |
| This is already reported and patch was proposed. Here: #30006 |
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:47 | admin | set | github: 74734 |
| 2017-10-23 17:03:01 | berker.peksag | set | status: open -> closedsuperseder: Deadlocks in `concurrent.futures.ProcessPoolExecutor`resolution: duplicatestage: resolved |
| 2017-06-21 19:56:59 | grzgrzgrz3 | set | nosy: + grzgrzgrz3messages: + |
| 2017-06-02 09:15:57 | Roberto Martínez | create |