https://bugs.winehq.org/show_bug.cgi?id=46107
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Altium Designer 18 page |Altium Designer 18.x - 20.x |faults when launched |crashes on startup
--- Comment #28 from Anastasius Focht focht@gmx.net --- Hello Tom,
--- quote --- Something is changed. With Wine-staging 5.7, instead of page fault, the X2.exe process becomes a zombi process. --- quote ---
the original msxml problem is still there. The application builtin exception/error handling (uses madExcept lib) is messed up due to bug 49011 (unfortunate regression that slipped into Wine 5.7 release), causing the zombie process.
--- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/Altium/AD18
$ WINEDEBUG=+seh,+relay,+msxml wine ./X2.EXE >>log.txt 2>&1 ... 002f:trace:msxml:xmlnodemap_get_item (0x20d8650)->(7 0x52e640) 002f:trace:msxml:domelem_get_item (0x7fc64839bba0)->(7 0x52e640) 002f:Call ole32.GetErrorInfo(00000000,0052e578) ret=7fc638749a19 002f:Ret ole32.GetErrorInfo() retval=00000001 ret=7fc638749a19 002f:Call KERNEL32.FormatMessageW(00003300,00000000,8007000e,00000000,0052e3f8,6e65282000000000,00000000) ret=7fc638463db2 002f:Call ntdll.RtlAllocateHeap(00010000,00000008,00000022) ret=7b028a38 002f:Ret ntdll.RtlAllocateHeap() retval=020d8970 ret=7b028a38 002f:Ret KERNEL32.FormatMessageW() retval=00000010 ret=7fc638463db2 ... 002f:Call KERNEL32.RaiseException(0eedfade,00000001,00000007,0052e538) ret=7fc638423ca6 002f:Call ntdll.memcpy(0052e388,0052e538,00000038) ret=7b00f656 002f:Ret ntdll.memcpy() retval=0052e388 ret=7b00f656 002f:trace:seh:raise_exception code=eedfade flags=1 addr=0x7b00f665 ip=7b00f665 tid=002f 002f:trace:seh:raise_exception info[0]=00007fc638d7a196 002f:trace:seh:raise_exception info[1]=00007fc643d36ca0 002f:trace:seh:raise_exception info[2]=0000000000000000 002f:trace:seh:raise_exception info[3]=0000000000000000 002f:trace:seh:raise_exception info[4]=0000000000000000 002f:trace:seh:raise_exception info[5]=0000000000000000 002f:trace:seh:raise_exception info[6]=0000000000000000 002f:trace:seh:raise_exception rax=000000000052e388 rbx=00007fc643d36ca0 rcx=000000000052e368 rdx=0000000000000036 002f:trace:seh:raise_exception rsi=0000000000000007 rdi=000000000052e430 rbp=000000000052e468 rsp=000000000052e340 002f:trace:seh:raise_exception r8=0000000000000000 r9=000000000052db40 r10=0000000000000000 r11=0000000000000000 002f:trace:seh:raise_exception r12=0000000000000000 r13=00007fc638d73198 r14=0000000000000000 r15=0000000000000000 002f:trace:seh:RtlVirtualUnwind type 1 rip 7b00f665 rsp 52e340 ... 002f:Call oleaut32.SysAllocStringLen(7fc643d40ce0 L"Out of memory",0000000d) ret=7fc638424fe3 ... 002f:Call KERNEL32.MultiByteToWideChar(0000fde9,00000000,7fc6387486d9 "EOleException\xa1",0000000d,7fc643d40cb0,7fc60000000e) ret=7fc63842c2eb 002f:Call ntdll.RtlUTF8ToUnicodeN(7fc643d40cb0,0000001c,0052c7a0,7fc6387486d9,0000000d) ret=7b01fb0e 002f:Ret ntdll.RtlUTF8ToUnicodeN() retval=00000000 ret=7b01fb0e 002f:Ret KERNEL32.MultiByteToWideChar() retval=0000000d ret=7fc63842c2eb 002f:Call KERNEL32.MultiByteToWideChar(0000fde9,00000000,7fc638748479 "EOleSysErrorw",0000000c,7fc643d40cb0,7fc60000000d) ret=7fc63842c2eb 002f:Call ntdll.RtlUTF8ToUnicodeN(7fc643d40cb0,0000001a,0052c7a0,7fc638748479,0000000c) ret=7b01fb0e 002f:Ret ntdll.RtlUTF8ToUnicodeN() retval=00000000 ret=7b01fb0e 002f:Ret KERNEL32.MultiByteToWideChar() retval=0000000c ret=7fc63842c2eb 002f:Call KERNEL32.MultiByteToWideChar(0000fde9,00000000,7fc63874831f "EOleError0\x83t8\xc6\x7f",00000009,7fc643d40cb0,7fc60000000a) ret=7fc63842c2eb 002f:Call ntdll.RtlUTF8ToUnicodeN(7fc643d40cb0,00000014,0052c7a0,7fc63874831f,00000009) ret=7b01fb0e 002f:Ret ntdll.RtlUTF8ToUnicodeN() retval=00000000 ret=7b01fb0e 002f:Ret KERNEL32.MultiByteToWideChar() retval=00000009 ret=7fc63842c2eb ... 002f:Call KERNEL32.FindResourceA(7fc638410000,7fc638ceafdc "TMADEXCEPT",0000000a) ret=7fc638ceafd7 ... 002f:Call KERNEL32.GetThreadContext(00000180,7fc638080000) ret=7fc638d37ebb 0034:Call PE DLL (proc=0x7fc640339c7c,module=0x7fc640290000 L"Altium_SQLite3_x64.dll",reason=THREAD_DETACH,res=(nil)) 0034:Ret PE DLL (proc=0x7fc640339c7c,module=0x7fc640290000 L"Altium_SQLite3_x64.dll",reason=THREAD_DETACH,res=(nil)) retval=1 ... 0034:Call ntdll.NtClose(00000000) ret=7b0366a4 0033:err:ntdll:RtlpWaitForCriticalSection section 0x7bd3fd00 "/home/focht/projects/wine/mainline-src/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0033, blocked by 0034, retrying (60 sec) --- snip ---
In general I suggest to always test the originally reported app version first with each Wine release. While being useful to a certain extent, mixing/switching different vendor product releases (AD 18.x, 19.x, 20.x) and Wine flavours (Wine, Wine-Staging) should always come second - unless you know that the underlying root cause is always the same.
$ sha1sum OfflineSetup_Altium_Designer_Public_18_1_9.zip ed78dc04efadd4ad2b515cb9ca95d32d418d9189 OfflineSetup_Altium_Designer_Public_18_1_9.zip
$ du -sh OfflineSetup_Altium_Designer_Public_18_1_9.zip 2.2G OfflineSetup_Altium_Designer_Public_18_1_9.zip
$ wine --version wine-5.7
Regards