Access to ProcessEventsToSignal's bSignal is racy

...so spell out its single use, locking the appropriate mutex around the access

Change-Id: I8e8f47de1979f5a80cf1ad65e5ec24d25145c463
Reviewed-on: https://gerrit.libreoffice.org/42908
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>

1 files changed, 9 insertions, 1 deletions

diff --git a/vcl/source/uitest/uno/uiobject_uno.cxx b/vcl/source/uitest/uno/uiobject_uno.cxx
index b68b15aeb5df..a32ff6542198 100644
--- a/vcl/source/uitest/uno/uiobject_uno.cxx
+++ b/vcl/source/uitest/uno/uiobject_uno.cxx
@@ -96,7 +96,15 @@ IMPL_LINK_NOARG(ExecuteWrapper, ExecuteActionHdl, Timer*, void)
             aIdle.Start();
         }
 
-        Scheduler::ProcessEventsToSignal(mbSignal);
+        for (;;) {
+            {
+                std::unique_lock<std::mutex> lock(mMutex);
+                if (mbSignal) {
+                    break;
+                }
+            }
+            Application::Reschedule();
+        }
         std::unique_lock<std::mutex> lock(mMutex);
         while (!mbSignal)
         {