[issue34059] multiprocessing deadlock

Guillaume Perrault-Archambault added the comment: A friend of mine has suggested a fix that seems to work for now (upgrade numpy from 1.14.3 to 1.14.5). This makes no sense at all but it does seem to work for now. I have a strong suspicion that this is just masking the problem and that it

[issue34059] multiprocessing deadlock

Guillaume Perrault-Archambault added the comment: Hi Victor and Yang, Thanks for your fast replies. I did initially think it could be a torch issue. Indeed, I have an equivalent numpy testcase that does not deadlock. However, the fact that it gets stuck inside a multiprocessing wait

[issue34059] multiprocessing deadlock

STINNER Victor added the comment: IMHO it's an issue with your usage of the torch module which is not part of the Python stdlib, so I suggest to close this issue as "third party" or "not a bug". -- nosy: +vstinner ___ Python tracker

[issue34059] multiprocessing deadlock

Windson Yang added the comment: I'm can't reproduce the deadlock, maybe it's related to torch package? Can you try without torch to see if this happens again? -- nosy: +Windson Yang ___ Python tracker

[issue34059] multiprocessing deadlock

New submission from Guillaume Perrault-Archambault : The simple code attached causes a deadlock in Linux. Problem is I have to slightly muck around with it depending on the distro and python version to get it to deadlock. On the cluster I use the most (python 3.6.3, CentOS Linux release