Closed MichaelRawson closed 20 hours ago
In #577 I failed to notice that FMB calls Timer::disableLimitEnforcement more than once for some reason. This causes FMB to hang on success (!). Oops.
Timer::disableLimitEnforcement
Fix that by using an atomic flag rather than a mutex. This also seems more intuitive to me in retrospect.
After discussion with @quickbeam123 , probably std::mutex::try_lock is a better option. (or std::recursive_mutex)
std::mutex::try_lock
std::recursive_mutex
In #577 I failed to notice that FMB calls
Timer::disableLimitEnforcement
more than once for some reason. This causes FMB to hang on success (!). Oops.Fix that by using an atomic flag rather than a mutex. This also seems more intuitive to me in retrospect.