Message294256
Thanks to everyone jumping in.
I need no convincing that mixing forks and threads isn't just a problem but a problem factory. Given that the rest of this code seems to try to avoid similar deadlocks with similar mutexes, I figured we'd want to include this mutex to make a best-effort at being safe here. That made it worth reporting. To be sure, I still believe that the application code that led us here needs deeper fixes to address the fork/thread problems. |
|
Date |
User |
Action |
Args |
2017-05-23 15:37:09 | Louis Brandy | set | recipients:
+ Louis Brandy, gregory.p.smith, vstinner, pixelbeat, lukasz.langa, cooperlees, drothera, phantez, Piotr Wysocki |
2017-05-23 15:37:09 | Louis Brandy | set | messageid: <1495553829.72.0.158580582698.issue30395@psf.upfronthosting.co.za> |
2017-05-23 15:37:09 | Louis Brandy | link | issue30395 messages |
2017-05-23 15:37:09 | Louis Brandy | create | |
|