The notifying thread does not need to hold the lock on the same mutex as the one held by the waiting thread(s); in fact doing so is a pessimization.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/adbd-client.cpp b/src/adbd-client.cpp
index 25aefa8..597e69f 100644
--- a/src/adbd-client.cpp
+++ b/src/adbd-client.cpp
@@ -131,7 +131,7 @@ g_debug("%s %s", G_STRLOC, G_STRFUNC);
 
 g_debug("%s %s", G_STRLOC, G_STRFUNC);
         // set m_pkresponse and wake up the waiting worker thread
-        std::lock_guard<std::mutex> lk(m_pkresponse_mutex);
+        //std::lock_guard<std::mutex> lk(m_pkresponse_mutex);
         //std::unique_lock<std::mutex> lk(m_pkresponse_mutex);
 g_debug("%s %s", G_STRLOC, G_STRFUNC);
         m_pkresponse = response;