Opened 7 months ago

Last modified 4 months ago

#13599 assigned Support Requests

condition_variable::timed_wait never returns

Reported by: steven.cook@… Owned by: viboes
Milestone: To Be Determined Component: thread
Version: Boost 1.65.0 Severity: Problem
Keywords: Cc:

Description

boost::condition_variable::timed_wait never returns if compiled with -DBOOST_THREAD_HAS_CONDATTR_SET_CLOCK_MONOTONIC.

this_thread::sleep and thread::timed_join exhibit the same problem, but both these functions are documented as deprecated. However condition_variable::timed_wait is not documented as deprecated.

This can be worked around by using condition_variable::wait_for.

The following simple test program demonstrates the problem in that it hangs forever. Removing the #define makes it return after one second.

#define BOOST_THREAD_HAS_CONDATTR_SET_CLOCK_MONOTONIC

#include <boost/thread.hpp>
#include <iostream>

int main( int argc, char* argv[] )
{
    boost::condition_variable cv;
    boost::mutex m;
    boost::mutex::scoped_lock lock( m );

    cv.timed_wait( lock, boost::posix_time::seconds( 1 ) );
    std::cout << "wait_for has returned" << std::endl;

    return 0;
}

Change History (4)

comment:1 Changed 5 months ago by viboes

condition_variable::timed_wait should be documented as deprecated.

Thanks for the report anyway, I would try to fix it.

comment:2 Changed 5 months ago by viboes

Owner: changed from Anthony Williams to viboes
Status: newassigned

comment:3 Changed 5 months ago by viboes

On which platform are you executing your program? Does the platform provide condition variables with monotonic clocks?

In principle, Boost.Thread defines BOOST_THREAD_HAS_CONDATTR_SET_CLOCK_MONOTONIC when know that this is the case. You should define it only if you are sure the platform provides it and Boost.Thread doesn't do it itself.

comment:4 Changed 4 months ago by viboes

Type: BugsSupport Requests

Moved to support until we have answer to the questions

Note: See TracTickets for help on using tickets.