http://bugs.winehq.org/show_bug.cgi?id=21493
Summary: Vampire Bloodlines crashes after loading a new game Product: Wine Version: 1.1.37 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: directx-dsound AssignedTo: wine-bugs@winehq.org ReportedBy: i30817@gmail.com
As in the title. Installed unoffical patch 6.7. The game also does a lot of resolution switches when playing the movies, but that may be because of me using two monitors. tried to capture the output with "wine vampire.exe | tee bug.txt" but the file was empty after crashing ... (but the errors appeared on screen).
Regardless the most common (and constant) error before crashing is this:
=64280/65536 (64280/65536), primary_mixpos=21428, writepos=42596, mixlen=15188 err:dsound:DSOUND_MixOne Fatal error. Under/Overflow? primary_done=67032, mixpos=64280/65536 (64280/65536), primary_mixpos=21428, writepos=42596, mixlen=15188 err:dsound:DSOUND_MixOne Fatal error. Under/Overflow? primary_done=67032, mixpos=64280/65536 (64280/65536), primary_mixpos=21428, writepos=42596, mixlen=15188
http://bugs.winehq.org/show_bug.cgi?id=21493
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|directx-dsound |-unknown Severity|major |normal
--- Comment #1 from Jeff Zaroyko jeffz@jeffz.name 2010-01-25 15:56:04 --- not major: http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity
attach terminal output as a text file by running with: wine vampire.exe 2> log.txt
If you have two displays setup, it's likely the game cannot find an acceptable display mode and will crash.
http://bugs.winehq.org/show_bug.cgi?id=21493
--- Comment #2 from paulo i30817@gmail.com 2010-01-26 06:02:29 --- Created an attachment (id=25892) --> (http://bugs.winehq.org/attachment.cgi?id=25892) zipped log
http://bugs.winehq.org/show_bug.cgi?id=21493
--- Comment #3 from paulo i30817@gmail.com 2010-01-26 06:03:19 --- attached the log.(i ran it now with only one monitor, but it crashed anyway).
http://bugs.winehq.org/show_bug.cgi?id=21493
paulo i30817@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.1.37 |1.1.36
--- Comment #4 from paulo i30817@gmail.com 2010-01-26 09:27:57 --- My wine version is actually 1.1.36. Made the mistake of thinking that ubuntu had it current.
http://bugs.winehq.org/show_bug.cgi?id=21493
--- Comment #5 from paulo i30817@gmail.com 2010-01-26 13:26:53 --- Created an attachment (id=25901) --> (http://bugs.winehq.org/attachment.cgi?id=25901) Game log
You might be interrested to know the game itself has a log that it flushes when crashed. Here it is.
http://bugs.winehq.org/show_bug.cgi?id=21493
--- Comment #6 from Jeff Zaroyko jeffz@jeffz.name 2010-01-26 13:32:30 --- (In reply to comment #5)
Created an attachment (id=25901)
--> (http://bugs.winehq.org/attachment.cgi?id=25901) [details]
Game log
You might be interrested to know the game itself has a log that it flushes when crashed. Here it is.
That game log might be preventing useful output, instead can you run with: wine winedbg vampire.exe | tee log.txt type c press enter
Then attach the new log.txt
http://bugs.winehq.org/show_bug.cgi?id=21493
--- Comment #7 from paulo i30817@gmail.com 2010-01-26 15:18:07 --- Running with a debugger detects it right away, and shows a message and black screens.
Anyway, it doesn't flush it to std err, but to file.
http://bugs.winehq.org/show_bug.cgi?id=21493
--- Comment #8 from Jeff Zaroyko jeffz@jeffz.name 2010-01-26 15:19:50 --- That's too bad, because the real crash is hard to see if the game's crash handler interprets it.
Try attaching to the process with winedbg after starting the program normally, http://wiki.winehq.org/Backtraces
http://bugs.winehq.org/show_bug.cgi?id=21493
--- Comment #9 from paulo i30817@gmail.com 2010-01-26 15:46:04 --- Ok i followed the process there. 1) started the game 2) started the debugger while the game was in the main menu. 3) attached to the process 4) clicked start game on the game
Got this on the debugger:
Wine-dbg>info process pid threads parent executable (all id:s are in hex) 00000008 6 00000000 'vampire.exe' 0000000e 4 0000000a 'services.exe' 00000011 4 0000000e 'winedevice.exe' 00000019 3 0000000e 'winedevice.exe' 00000022 1 00000008 'explorer.exe' 00000026 2 00000008 '~e5.0001' 00000032 1 00000008 'winedbg.exe' Wine-dbg>attach 0x12 Can't attach process 0012: error 87 Wine-dbg>attach 0x8 Can't attach process 0008: error 5 Wine-dbg>info process pid threads parent executable (all id:s are in hex) 0000000e 4 0000000a 'services.exe' 00000011 4 0000000e 'winedevice.exe' 00000019 3 0000000e 'winedevice.exe' 00000034 6 00000000 'vampire.exe' 00000038 1 00000034 'explorer.exe' 0000003c 2 00000034 '~e5.0001' Wine-dbg>attach 0x34 0x68000832 GLIBC_2+0x832 in ld-linux.so.2: ret Wine-dbg>set $BreakOnFirstChance=0 Wine-dbg>cont Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x4d991190). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:4d991190 ESP:0032d9f4 EBP:0032da3c EFLAGS:00210202( R- -- I - - - ) EAX:00000000 EBX:4dbb2ff4 ECX:00000001 EDX:7d8f1740 ESI:00000000 EDI:7d8f1740 Stack dump: 0x0032d9f4: 7c3d8a98 7c367ca0 0032da3c 4d991e81 0x0032da04: 7ca69268 00000000 00000000 00000000 0x0032da14: 00000000 7c36690c 0000000c 4d973d81 0x0032da24: 7d8f1710 001741a8 4d99115b 4dbb2ff4 0x0032da34: 7c3c3cf0 00000001 0032daec 4d974fc7 0x0032da44: 7d8f1740 00000000 00000000 00000001 Backtrace: =>0 0x4d991190 radeonEmitVec16+0x40() in r300_dri.so (0x0032da3c) 1 0x4d974fc7 in r300_dri.so (+0x2cfc7) (0x0032daec) 2 0x4da23e66 in r300_dri.so (+0xdbe66) (0x0032db5c) 3 0x4da23fee in r300_dri.so (+0xdbfee) (0x0032db9c) 4 0x4da1b1ce in r300_dri.so (+0xd31ce) (0x0032dbbc) 5 0x20348d14 in wined3d (+0x68d14) (0x0032df6c) 6 0x2031e251 in wined3d (+0x3e251) (0x0032dfbc) 7 0x3bf4b516 in d3d9 (+0xb516) (0x0032e01c) 8 0x2a01203f in shaderapidx9 (+0x1203f) (0x2a068570) 9 0x00490105 (0x2a0527f0) 10 0x2a012580 in shaderapidx9 (+0x12580) (0x2a012470) 0x4d991190 radeonEmitVec16+0x40 in r300_dri.so: movl 0x0(%esi),%edx Wine-dbg>
do you wan't me to continue?
http://bugs.winehq.org/show_bug.cgi?id=21493
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #10 from Jeff Zaroyko jeffz@jeffz.name 2010-01-26 15:59:34 --- (In reply to comment #9)
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x4d991190). Backtrace: =>0 0x4d991190 radeonEmitVec16+0x40() in r300_dri.so (0x0032da3c) 1 0x4d974fc7 in r300_dri.so (+0x2cfc7) (0x0032daec) 2 0x4da23e66 in r300_dri.so (+0xdbe66) (0x0032db5c) 3 0x4da23fee in r300_dri.so (+0xdbfee) (0x0032db9c) 4 0x4da1b1ce in r300_dri.so (+0xd31ce) (0x0032dbbc) 5 0x20348d14 in wined3d (+0x68d14) (0x0032df6c) 6 0x2031e251 in wined3d (+0x3e251) (0x0032dfbc) 7 0x3bf4b516 in d3d9 (+0xb516) (0x0032e01c) 8 0x2a01203f in shaderapidx9 (+0x1203f) (0x2a068570) 9 0x00490105 (0x2a0527f0) 10 0x2a012580 in shaderapidx9 (+0x12580) (0x2a012470) 0x4d991190 radeonEmitVec16+0x40 in r300_dri.so: movl 0x0(%esi),%edx do you wan't me to continue?
No, that's good. It shows the crash is in your video drivers, not Wine. Report the bug to your distro/r300_dri developers or upgrade to a newer version and see if the bug is still present.
Resolving invalid.
http://bugs.winehq.org/show_bug.cgi?id=21493
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Jeff Zaroyko jeffz@jeffz.name 2010-01-26 16:00:21 --- Closing invalid.