diff options
author | sfan5 <sfan5@live.de> | 2022-04-30 16:04:19 +0200 |
---|---|---|
committer | sfan5 <sfan5@live.de> | 2022-05-02 20:54:55 +0200 |
commit | 663c9364289dae45aeb86a87cba826f577d84a9c (patch) | |
tree | eecbde60c46f941a7185cff4e88bef2bd5768e11 | |
parent | 56a558baf8ef43810014347ae624cb4ef70b6aa3 (diff) | |
download | minetest-663c9364289dae45aeb86a87cba826f577d84a9c.tar.gz minetest-663c9364289dae45aeb86a87cba826f577d84a9c.tar.bz2 minetest-663c9364289dae45aeb86a87cba826f577d84a9c.zip |
Fix synchronization issue at thread start
If a newly started thread immediately exits then m_running would
immediately be set to false again and the caller would be stuck
waiting for m_running to become true forever.
Since a mutex for synchronizing startup already exists we can
simply move the while loop into it.
see also: #5134 which introduced m_start_finished_mutex
-rw-r--r-- | src/threading/thread.cpp | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/threading/thread.cpp b/src/threading/thread.cpp index 5cfc60995..ef025ac1d 100644 --- a/src/threading/thread.cpp +++ b/src/threading/thread.cpp @@ -121,12 +121,12 @@ bool Thread::start() return false; } - // Allow spawned thread to continue - m_start_finished_mutex.unlock(); - while (!m_running) sleep_ms(1); + // Allow spawned thread to continue + m_start_finished_mutex.unlock(); + m_joinable = true; return true; |