You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry if this isn't the right place for boost issues. Please close if this should go somewhere else.
Hi, I'm trying to understand the behavior of thread_pool::wait, the documentation (Boost 1.83) says:
This function blocks until the threads in the pool have completed. If stop() is not called prior to wait(), the wait() call will wait until the pool has no more outstanding work.
boost::asio::thread_pool thread_pool(10);
...
boost::asio::post(thread_pool_, task0);
....
thread_pool.wait(); //stop was not called so should just wait until the pool has no more outstanding work.boost::asio::post(thread_pool_, task9999); // hangs forever
Since I didn't call stop I would expect to be able to post more things to the pool but it appears wait actually shutdowns the pool even if stop was not called.
The text was updated successfully, but these errors were encountered:
Sorry if this isn't the right place for boost issues. Please close if this should go somewhere else.
Hi, I'm trying to understand the behavior of
thread_pool::wait
, the documentation (Boost 1.83) says:Source: https://www.boost.org/doc/libs/1_83_0/doc/html/boost_asio/reference/thread_pool/wait.html
If I have something like:
Since I didn't call
stop
I would expect to be able to post more things to the pool but it appearswait
actually shutdowns the pool even ifstop
was not called.The text was updated successfully, but these errors were encountered: