https://bugs.winehq.org/show_bug.cgi?id=46222
--- Comment #7 from Greg Smith codedonewell@gmail.com --- I've had some success at finding causes with the following WINEDEBUG setting: fixme+all,trace+all,trace-heap,+relay
I have the following RelayExclude setting: ntdll.RtlEnterCriticalSection;ntdll.RtlTryEnterCriticalSection;ntdll.RtlLeaveCriticalSection;kernel32.48;kernel32.49;kernel32.94;kernel32.95;kernel32.96;kernel32.97;kernel32.98;kernel32.TlsGetValue;kernel32.TlsSetValue;kernel32.FlsGetValue;kernel32.FlsSetValue;kernel32.SetLastError;KERNEL32.GetWindowsDirectoryW;KERNEL32.SetCurrentDirectoryW;advapi32.RegSetValueExW;advapi32.RegCreateKeyExW;advapi32.RegCloseKey;ucrtbase.memcmp;ucrtbase.malloc;ucrtbase.free;ntdll.RtlAllocateHeap;ntdll.RtlFreeHeap;KERNEL32.lstrcmpA;KERNEL32.LocalAlloc;ntdll.RtlReAllocateHeap;ucrtbase.memcpy;ucrtbase.memmove;ucrtbase.isspace;ucrtbase.memchr;ucrtbase._dtest;ucrtbase.memset;ucrtbase.realloc;ucrtbase.memset;KERNEL32.GetLocaleInfoA;KERNEL32.GetLocaleInfoW;ntdll.RtlReleaseSRWLockExclusive;ntdll.RtlAcquireSRWLockExclusive;ntdll.RtlReleaseSRWLockShared;ntdll.RtlAcquireSRWLockShared;ucrtbase.floorf;user32.GetKeyState;ucrtbase.ceilf;ucrtbase._lrotl;ucrtbase.round;ucrtbase._lrotr
I redirect the output to a file. As you may expect the log file is huge (70-160Gb). I have scripts to split the threads and timestamp the names, to make it easier to jump around, but I have no short cut for the log work of crawling over the log files.
If you want to work together on this, join LUG in starcitizen and lets chat. I do not have the problem, so you will need to create the logs, compress them and put them somehwere where we can both look at them.