https://bugs.winehq.org/show_bug.cgi?id=52846
Bug ID: 52846 Summary: Capture One 22 fails to start with wbemprox related crashes Product: Wine Version: 7.6 Hardware: x86-64 URL: https://www.captureone.com/en/new-update/capture-one-2 2 OS: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: xerox.xerox2000x@gmail.com Distribution: Debian
Created attachment 72244 --> https://bugs.winehq.org/attachment.cgi?id=72244 +wbemprox,+mountmgr,+seh
Hi, a user reported trouble with this program on the forum so i gave it a try.
Apparently for him it crashed inside wbemprox, but the crash is for me different, and more unfortunate it differs from time to time, and every now and then it does`t crash at all but just starts.... But all crashes look similar like: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at System.Management.SecuredIEnumWbemClassObjectHandler.Clone_(IEnumWbemClassObject& ppEnum) at System.Management.ManagementObjectCollection.GetEnumerator()
I attached one of the crashes to this report (+seh,+wbemprox,+mountmgr).
One thing that can be seen it queries for property "Characteristics" from win32_processor, that is afaics missing, but that is probably not the cause of the crashes; to rule that out could it be added?
It might be due to mountmgr.sys insufficiencies, but i cannot tell really for sure. Anyway, one way to reliably get the program started 100% is disabling mountmgr.sys and/or wbmprox...
(Note: I installed native dotnet48, d3dcompiler_47 and arial via winetricks)
https://bugs.winehq.org/show_bug.cgi?id=52846
--- Comment #1 from Louis Lenders xerox.xerox2000x@gmail.com --- Forgot to add forum thread: https://forum.winehq.org/viewtopic.php?f=2&t=36452
https://bugs.winehq.org/show_bug.cgi?id=52846
--- Comment #2 from Hans Leidekker hans@meelstraat.net --- (In reply to Louis Lenders from comment #1)
It performs the same query simultaneously from 2 threads, which involves an ioctl to mountmgr:
0144:trace:wbemprox:wbem_services_ExecQuery 0000000000F03430, L"WQL", L"SELECT Antecedent, Dependent from Win32_LogicalDiskToPartition", 0x10, 000000000000000 0, 000000001E1DEF08 ... 0160:trace:wbemprox:wbem_services_ExecQuery 0000000026767CC0, L"WQL", L"SELECT Antecedent,Dependent FROM win32_logicaldisktopartition", 0x10, 0000000000000000 , 0000000032DFEBE8
Unfortunately the backtraces aren't very useful.