https://bugs.winehq.org/show_bug.cgi?id=36697
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- URL|http://www.playon.tv/downlo |https://web.archive.org/web |ads/playon/ |/20210302110846/http://dl15 | |.afterdawn.com/download/7a5 | |e997ae708ddd2f9550663dc4d40 | |cd/603e1ca1/n-z/PlayOnSetup | |.3.9.14.exe Status|NEW |RESOLVED Resolution|--- |FIXED Fixed by SHA1| |09e98be24350a7a8306cc6cd730 | |2f94eae770afc Component|-unknown |rpc Summary|64-bit InstallShield engine |64-bit InstallShield engine |COM server 'ISBEW64.exe' |COM server 'ISBEW64.exe' |occasionally crashes on OLE |crashes or hangs (32-bit |teardown (32-bit |InstallShield based |InstallShield based |installers in 64-bit |installers in 64-bit |WINEPREFIX) |WINEPREFIX) |
--- Comment #23 from Anastasius Focht focht@gmx.net --- Hello folks,
the problems were indeed fixed some years ago. There were different manifestations of the problems with 64-bit InstallShield engine COM server 'ISBEW64.exe'.
* COM server crashes consistently at early point of installation (page fault or stack overflow) * COM server crashes at late point but not consistently (page fault or stack overflow) * COM server hangs/zombifies due to preceding unhandled exceptions
It varies between apps (linked duplicate tickets). The initial crash was definitely the most common visible symptom up to Wine 2.4
I tested several installers linked from the duplicate bug reports with Wine 2.x releases.
* https://web.archive.org/web/20210302122901/http://dl15.afterdawn.com/downloa...
* https://web.archive.org/web/20140407232928/http://www.downloads.netgear.com/...
* https://web.archive.org/web/20140822001235mp_/http://d1heja5wzvsadj.cloudfro...
Wine 2.0 - 2.4
--- snip --- fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0x33f1dc L"C:\users\focht\Temp\{F11A34B6-CBA7-402B-B50E-65CFF56F31D7}\Disk1\data1.hdr" err:rpc:I_RpcReceive we got fault packet with status 0x3e6 fixme:ole:NdrClearOutParameters (0x33e4d0,0x7e150e7c,0x33e800): stub fixme:ole:NdrClearOutParameters (0x33e4d0,0x7e150ea6,0x33e6e4): stub fixme:ole:NdrClearOutParameters (0x33e4d0,0x7e150eaa,0x33e704): stub fixme:ole:NdrClearOutParameters (0x33e4d0,0x7e150ece,0x33e800): stub wine: Unhandled page fault on write access to 0x00000007 at address 0x7bc5bd3f (thread 005d), starting debugger... --- snip ---
Wine 2.5 - 2.9
--- snip --- fixme:ole:NdrClearOutParameters (0x33e260,0x7e14710e,0x33e59c): stub fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0x33f1dc L"C:\users\focht\Temp\{889CFF4A-1836-421C-A590-CC109D3653A0}\Disk1\data1.hdr" err:seh:setup_exception stack overflow 1680 bytes in thread 0070 eip 000000007bc9481c esp 0000000000750f80 stack 0x750000-0x751000-0x850000 --- snip ---
Wine 2.10 -> works for most app installers.
The following series of commits between Wine 2.9 and Wine 2.10 release were responsible for fixing the early crash.
* https://source.winehq.org/git/wine.git/commitdiff/5c81f8295e379bf09b51466eb3... ("rpcrt4: Store server thread handle in RpcServerProtseq.")
* https://source.winehq.org/git/wine.git/commitdiff/5c2083fd22d252c1d1c082d585... ("rpcrt4: Store listening pipe name in RpcConnection_np.")
* https://source.winehq.org/git/wine.git/commitdiff/10a6b33a93cd4ea33032077b8e... ("rpcrt4: Recreate listening pipe in rpcrt4_protseq_np_get_wait_array if needed.")
* https://source.winehq.org/git/wine.git/commitdiff/e98c7a59c26bdff7bad27e5864... ("rpcrt4: Wait for all active connections to be released before quiting server thread.")
* https://source.winehq.org/git/wine.git/commitdiff/09e98be24350a7a8306cc6cd73... ("rpcrt4: Wait for server threads to finish in RpcMgmtWaitServerListen.")
Unfortunately I've still encountered a small set of app installers which ran into hangs or stack overflows in 64-bit InstallShield engine process past Wine 2.10 release.
Example:
https://web.archive.org/web/20140822001235mp_/http://d1heja5wzvsadj.cloudfro...
Prerequisite: killing all (zombified) processes from previous runs and using a new WINEPREFIX.
Not every installer run resulted in a stack overflow which is a bit annoying.
I've identified another set of changes between Wine 3.0 and 3.1 release for fixing this problem. I will de-duplicate some linked bug reports as needed to document this.
$ wine --version wine-2.10
Regards