westonpace commented on PR #13651: URL: https://github.com/apache/arrow/pull/13651#issuecomment-1190817974
The root cause ended up being the global future waiter mutex. This mutex was not reset after a fork. So if a fork happened while this mutex was held then it would lead to deadlock in the child. We weren't encountering this in tests before because we would have released the mutex before we signaled the condition variable. Now that we signal the cv inside the mutex there is a small chance we could fork while the mutex was still being released. Since we wanted to remove the future waiter stuff anyways I just ripped it out instead of trying to find a way to properly reset the mutex. -- 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-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
