http://bugs.winehq.org/show_bug.cgi?id=36697
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Version|unspecified |1.7.18 URL| |http://www.playon.tv/downlo | |ads/playon/ Keywords| |download, Installer, win64 CC| |focht@gmx.net Resolution|DUPLICATE |--- Ever confirmed|0 |1 Summary|PlayOn won't install in a |64-bit InstallShield engine |64-bit WINEPREFIX |COM server 'ISBEW64.exe' | |occasionally crashes on OLE | |teardown (32-bit | |InstallShield based | |installers in 64-bit | |WINEPREFIX)
--- Comment #3 from Anastasius Focht focht@gmx.net --- Hello folks,
actually bug 24611 had multiple issues mixed together. I didn't explicitly mention this there since that bug was targeting WoW64 COM registry views synchronization (the main blocker).
Your backtrace highlights a shutdown race that occasionally happens in 64-bit InstallShield engine COM server which talks over standard marshaller to the 32-bit installer part.
The crash is harmless in the end as it happens in OLE server teardown phase (typelib/refcounting) but of course it scares people because it triggers 'winedbg'.
--- snip --- Unhandled exception: page fault on read access to 0x00000007 in 64-bit code (0x00007f11f0b1e5ec). Register dump: rip:00007f11f0b1e5ec rsp:000000000023f760 rbp:000000000004ef80 eflags:00010246 ( R- -- I Z- -P- ) rax:000000000005f850 rbx:0000000000000007 rcx:0000000000000007 rdx:0000000000000008 rsi:0000000000000000 rdi:0000000000000000 r8:0000000000000000 r9:000000000023f5a8 r10:000000000023f578 r11:0000000000000000 r12:000000000004efa0 r13:000000000005f0f0 r14:0000000000000000 r15:0000000000000000 ... Backtrace: =>0 0x00007f11f0b1e5ec VariantClear+0xdc() in oleaut32 (0x000000000004ef80) 1 0x00007f11f0b0c875 in oleaut32 (+0x4c874) (0x000000000004ef80) 2 0x00007f11f0b057ad in oleaut32 (+0x457ac) (0x0000000000000000) 3 0x0000000000401440 in isbew64 (+0x143f) (0x000000000041b960) 4 0x0000000000406486 in isbew64 (+0x6485) (0x000000000041b960) ... 0x00007f11f0b1e5ec VariantClear+0xdc in oleaut32: movzwl (%rbx),%eax Modules: Module Address Debug info Name (56 modules) PE 400000- 420000 Export isbew64 ELF 7b800000- 7bc73000 Dwarf kernel32<elf> -PE 7b820000- 7bc73000 \ kernel32 ELF 7be00000- 7c103000 Dwarf <wine-loader> ... Threads: process tid prio (all id:s are in hex) ... 0000002a (D) C:\users\lyriclover\Temp{336BCF94-D575-4E52-AA73-85C4B02D0543}\ISBEW64.exe 00000040 0 0000003e 0 0000002d 0 0000002b 0 <== --- snip ---
Anyway, your app needs .NET Framework 3.5 SP1 and Windows Media Player 9+
These prerequisites are not properly installed in 64-bit WINEPREFIX due to other known Wine bugs.
Even if .NET Framework installers report success in WoW64 environment (without 'winetricks') they are still broken in the end.
For WMP 9 you need a bi-arch installer because the installer detects WoW64 environment.
Various issues that only experts can properly diagnose and work around - it's not for the faint-hearted.
So yes, please use a 32-bit WINEPREFIX (WINEARCH=win32) to avoid all the mess.
I'll rechristen the bug because it still highlights a problem with Wine (albeit non-critical).
Regards