Threading: Prevent EventObject lost wakeup and fix Mutex destructor

The issue is that the mutex is unlocked before signaling the condition variable.
This can lead to a "lost wakeup" problem where a signal is sent when no thread is waiting, causing the signal to be lost and a waiting thread to potentially sleep forever.
The fix is to signal the condition variable while the mutex is still locked.

Author: Pagghiu

Libraries/Threading/Internal/ThreadingWindows.inl

@@ -6,7 +6,7 @@
 #include "../Threading.h"
 
 SC::Mutex::Mutex() { ::InitializeCriticalSection(&mutex.reinterpret_as<CRITICAL_SECTION>()); }
-SC::Mutex::~Mutex() { ::InitializeCriticalSection(&mutex.reinterpret_as<CRITICAL_SECTION>()); }
+SC::Mutex::~Mutex() { ::DeleteCriticalSection(&mutex.reinterpret_as<CRITICAL_SECTION>()); }
 void SC::Mutex::lock() { ::EnterCriticalSection(&mutex.reinterpret_as<CRITICAL_SECTION>()); }
 void SC::Mutex::unlock() { ::LeaveCriticalSection(&mutex.reinterpret_as<CRITICAL_SECTION>()); }
 

Libraries/Threading/Threading.cpp

@@ -64,6 +64,6 @@ void SC::EventObject::signal()
 {
     mutex.lock();
     isSignaled = true;
-    mutex.unlock();
     cond.signal();
+    mutex.unlock();
 }