-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Linux] boost::process:: child ::wait_until is not thread-safe #347
Comments
I deprecated them, they're generally unsafe. |
Can you update documentation with information about deprecation please? I can`t find this info |
I, too, would appreciate information on the deprecation. |
@klemens-morgenstern Following up on the previous comments, do you have any references on the rationale for the deprecation, so that I can better understand what the issue is and look for alternatives moving forward? |
They are fine on windows, but unsafe on linux. Therefor process cant provide a portable function that is safe. The recommendation is to use V2 and async_wait, so you can us an asio timer to create a timeout. |
Ah great, thank you very much for such a prompt response! |
Hi! I faced with the problem that my process hangs up while it uses wait_until() of child::process. So I watched boost code and find that boost::process:: child ::wait_until is not thread-safe
bug_wait_until.cpp.txt
out.txt
So can you update your documentation with this note please?
UPD: After I write this issue I found the same:
POSIX wait_for() crashes when multiple threads run it simultaneously
POSIX wait_for - stack overflow
child::wait_for() may block indefinitely
The text was updated successfully, but these errors were encountered: