You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/02/07 13:13:25 UTC

[GitHub] [arrow] pitrou commented on issue #12329: An unhandled race condition exists in `ThreadPool`

pitrou commented on issue #12329:
URL: https://github.com/apache/arrow/issues/12329#issuecomment-1031455289


   > When a fork happens the child (the one that gets the new pid) will not have any running threads except the thread that called fork.
   
   This is right. `fork()` only preserves the thread which called `fork()`.
   
   > We would then go into this branch and reinitialize the state before any worker thread could possibly be launched. I suppose however, if there were two user threads (e.g. created by the arrow library user and not worker threads in the thread pool) that simultaneously trigger calls to SpawnReal then we could get into a race condition.
   
   You mean user threads created in the forked child? Yes, that's basically possible. Probably not very common, but possible :-)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org