http://bugs.winehq.org/show_bug.cgi?id=18927
Summary: Unable to install Need For Speed Undercover, msiexec crash Product: Wine Version: unspecified Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: msi AssignedTo: wine-bugs@winehq.org ReportedBy: smkururu@rocketmail.com
Created an attachment (id=21773) --> (http://bugs.winehq.org/attachment.cgi?id=21773) crash log
Hi, I'm trying to install Need For Speed Undercover. When I run AutoRun.exe it says that msiexec has encountered serious problem blah blah blah, it crashed. I've tried to run msiexec directly (with wine of course) to check if it runs and it does.
http://bugs.winehq.org/show_bug.cgi?id=18927
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal
http://bugs.winehq.org/show_bug.cgi?id=18927
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Installer Component|msi |-unknown
--- Comment #1 from Ken Sharp kennybobs@o2.co.uk 2009-06-13 10:27:09 --- 1. What version of Wine? 2. NOT major. 3. What version of NFSU? 4. Did you try in a clean WINEPREFIX? and finally Try the latest git.
http://bugs.winehq.org/show_bug.cgi?id=18927
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |ABANDONED
--- Comment #2 from Austin English austinenglish@gmail.com 2010-03-11 17:20:09 --- No response in 8 months, abandoned.
http://bugs.winehq.org/show_bug.cgi?id=18927
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Vitaliy Margolen vitaliy@kievinfo.com 2010-03-11 20:27:39 --- Closing
http://bugs.winehq.org/show_bug.cgi?id=18927
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED CC| |focht@gmx.net Component|-unknown |msi Platform|x86-64 |Other Version|unspecified |1.1.23 Resolution|ABANDONED |FIXED Summary|Unable to install Need For |Need For Speed: Undercover |Speed Undercover, msiexec |fails to install (msiexec |crash |crash)
--- Comment #4 from Anastasius Focht focht@gmx.net 2011-06-16 07:41:18 CDT --- Hello,
received that game on original media for testing. The installer suffers from bug 12116 ("Progress bar does not appear during installation") but appears to install everything fine, albeit slow (~30 minutes).
Game protection:
--- snip --- -=[ ProtectionID v0.6.4.0 JULY]=- (c) 2003-2010 CDKiLLER & TippeX Build 07/08/10-17:57:05 Ready...
Scanning -> Z:\home\focht.wine\drive_c\Program Files\EA Games\Need for Speed Undercover\nfs.exe File Type : 32-Bit Exe (Subsystem : Win CUI / 3), Size : 16151824 (0F67510h) Byte(s) -> File Appears to be Digitally Signed @ Offset 0F66000h, size : 01510h / 05392 byte(s) [File Heuristics] -> Flag : 00000000000000000000000000000101 (0x00000005) [!] SecuROM Detected - Version 07.38.0012 [!] Possible CD/DVD-Key or Serial Check -> CDKey [CompilerDetect] -> Visual C++ 8.0 (Visual Studio 2005) - Scan Took : 0.198 Second(s)
Scanning -> Z:\home\focht.wine\drive_c\Program Files\EA Games\Need for Speed Undercover\paul.dll File Type : 32-Bit Dll (Subsystem : Win GUI / 2), Size : 262144 (040000h) Byte(s) [File Heuristics] -> Flag : 00000000000000001000000000000000 (0x00008000) [!] SecuROM Modified PA Module Detected [!] Possible CD/DVD-Key or Serial Check -> registration code [CompilerDetect] -> Visual C++ 8.0 (Visual Studio 2005) - Scan Took : 0.510 Second(s) --- snip ---
Game can be started in windowed mode with "-w".
The game itself crashed on my machine after start. A relay trace shows it tries to allocate a large chunk of memory (~600 MiB).
--- snip --- 0026:Call KERNEL32.VirtualAlloc(00000000,00600000,00003000,00000004) ret=00a3ab74 0026:Ret KERNEL32.VirtualAlloc() retval=04a90000 ret=00a3ab74 0026:Call KERNEL32.InitializeCriticalSection(04a90004) ret=006a9b44 0026:Ret KERNEL32.InitializeCriticalSection() retval=00000001 ret=006a9b44 0026:Call KERNEL32.GetLastError() ret=78132dba 0026:Ret KERNEL32.GetLastError() retval=00000000 ret=78132dba 0026:Call KERNEL32.GetLastError() ret=78132dba 0026:Ret KERNEL32.GetLastError() retval=00000000 ret=78132dba 0026:Call KERNEL32.GetLastError() ret=78132dba 0026:Ret KERNEL32.GetLastError() retval=00000000 ret=78132dba 0026:Call KERNEL32.VirtualAlloc(00000000,23900000,00003000,00000004) ret=00a3ab74 0026:Ret KERNEL32.VirtualAlloc() retval=00000000 ret=00a3ab74 0026:trace:seh:raise_exception code=c0000005 flags=0 addr=0xa35108 ip=00a35108 tid=0026 0026:trace:seh:raise_exception info[0]=00000001 0026:trace:seh:raise_exception info[1]=00000080 0026:trace:seh:raise_exception eax=00000000 ebx=00000000 ecx=00000080 edx=238ffa00 esi=00000080 edi=00000080 0026:trace:seh:raise_exception ebp=238fff80 esp=0237e7c0 cs=0073 ds=007b es=007b fs=0033 gs=003b flags=00010246 0026:trace:seh:call_vectored_handlers calling handler at 0x68bf8de9 code=c0000005 flags=0 0026:trace:seh:call_vectored_handlers handler at 0x68bf8de9 returned 0 0026:trace:seh:call_stack_handlers calling handler at 0xba8cd1 code=c0000005 flags=0 --- snip ---
I've checked /proc/pid/maps at the time of the crash and it seems the address space is too fragmented to find such a large free area. This is due to randomized address space feature where some system lib mappings lead to fragmentation of the the virtual address space.
You can temporarily turn this feature off:
--- snip --- $ sudo bash -c "echo 0 >/proc/sys/kernel/randomize_va_space" --- snip ---
and the game should now start (did in my case).
Marking this bug fixed.
Regards
http://bugs.winehq.org/show_bug.cgi?id=18927
Alex Bradbury asb@asbradbury.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |asb@asbradbury.org
--- Comment #5 from Alex Bradbury asb@asbradbury.org 2011-06-16 14:34:08 CDT --- (In reply to comment #4)
I've checked /proc/pid/maps at the time of the crash and it seems the address space is too fragmented to find such a large free area. This is due to randomized address space feature where some system lib mappings lead to fragmentation of the the virtual address space.
You can temporarily turn this feature off:
--- snip --- $ sudo bash -c "echo 0 >/proc/sys/kernel/randomize_va_space" --- snip ---
and the game should now start (did in my case).
`setarch $(uname -m) -R bash` and then launching wine from that terminal (or just setarching wine directly) should do the same thing without needing root privileges or applying the setting system-wide.
http://bugs.winehq.org/show_bug.cgi?id=18927
--- Comment #6 from Anastasius Focht focht@gmx.net 2011-06-17 03:32:44 CDT --- Hello Alex,
--- quote --- `setarch $(uname -m) -R bash` and then launching wine from that terminal (or just setarching wine directly) should do the same thing without needing root privileges or applying the setting system-wide. --- quote ---
Thanks for the tip, I was unaware of '-R' option to enable it "locally" ;-)
I disable it globally once debugging sessions start so I don't need to keep track of this when switching between several terminals. Saves much hassle when retaining soft and hard breakpoints through different debugging sessions.
Regards
http://bugs.winehq.org/show_bug.cgi?id=18927
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Alexandre Julliard julliard@winehq.org 2011-06-24 17:43:41 CDT --- Closing bugs fixed in 1.3.23.
-
wine-bugs＠winehq.org