[Bug 53082] New: "explorer: Create clipboard manager thread when creating a desktop." causes hangs on wine startup

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=53082

            Bug ID: 53082
           Summary: "explorer: Create clipboard manager thread when
                    creating a desktop." causes hangs on wine startup
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: programs
          Assignee: wine-bugs at winehq.org
          Reporter: martin at martin.st
                CC: jacek at codeweavers.com
   Regression SHA1: d8a74e5cf9f259c5ec9480e74d286c93609b8d9c
      Distribution: ---

Since this commit, d8a74e5cf9f259c5ec9480e74d286c93609b8d9c "explorer: Create
clipboard manager thread when creating a desktop.", hangs occasionally when
setting up a new wineprefix. (It's possible that it also hangs when starting
wine with a preexisting wineprefix, but I pinpointed it for the init procedure
when setting up a fresh wineprefix.)

I've built wine headless (I only run command line executables), i.e. configured
with "--without-x" (on Linux). I've reproduced this on arm32, but it's
plausible that the same can happen on other architectures, too.

When bootstrapping a new wineprefix (setting WINEPREFIX to a new, nonexistent
directory, running "wine wineboot"), it can hang, printing errors like these:

0048:err:sync:RtlpWaitForCriticalSection section 7BC8A3F0
"../src/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0048,
blocked by 0054, retrying (60 sec)
0048:err:sync:RtlpWaitForCriticalSection section 7BC8A3F0
"../src/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0048,
blocked by 0054, retrying (60 sec)


Did this commit trigger some race condition when bootstrapping the environment?

This issue doesn't happen every time - when testing setup of a new wineprefix,
it happens maybe once in 5-10 attempts.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.