http://bugs.winehq.org/show_bug.cgi?id=15496
Summary: Rome Total War always crashes on certain maps Product: Wine Version: 1.1.5 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: robert.munteanu@gmail.com
Created an attachment (id=16414) --> (http://bugs.winehq.org/attachment.cgi?id=16414) WINEDEBUG=warn+all log and back trace
Please note that this is not a duplicate of http://bugs.winehq.org/show_bug.cgi?id=13501, since I have turned battlefield shadows off and other battles ( most ) work properly.
The crashes are related to settlement sieges in two ( so far ) cities:
- Byzantium - Narbo Martius
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #1 from Lei Zhang thestig@google.com 2008-10-03 13:37:23 --- Does this demo include one of those maps / cause the same crash? http://www.gamershell.com/download_6784.shtml
What video card / driver version are you using?
--> Z:\home\robert\downloads\The Creative Assembly\Rome - Total War\RomeTW.exe Did you install the game properly?
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #2 from Robert Munteanu robert.munteanu@gmail.com 2008-10-03 14:14:02 --- 1. I'll try the demo in a couple of days and try to crash it. It seems though that at a later time that map worked ( siege defense, other wall style )
2. Video card/driver:
01:00.0 VGA compatible controller: nVidia Corporation GeForce 7100 GS (rev a1) NVidia binary driver 173.14.12
3. Game installation : it's copied from a windows installation. I'll try a fresh install as well.
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #3 from Lei Zhang thestig@google.com 2008-10-03 14:38:41 --- Please make sure a fresh install has the same problem, otherwise this bug is invalid. You should not copy installed programs from a Windows partition.
http://bugs.winehq.org/show_bug.cgi?id=15496
Stephen Mills smills15@cox.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |smills15@cox.net
--- Comment #4 from Stephen Mills smills15@cox.net 2008-10-14 21:19:40 --- Could you provide a saved game file that easily reproduces the crash? I know I have conquered at least one of those cities without issue, but I will try to confirm the problem.
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #5 from Robert Munteanu robert.munteanu@gmail.com 2008-11-20 07:24:49 --- Created an attachment (id=17368) --> (http://bugs.winehq.org/attachment.cgi?id=17368) Save game which reproduces the crash
Attack Campus Getae and assault. The crash is triggered 100% of the times on my installation.
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #6 from Stephen Mills smills15@cox.net 2008-12-15 18:45:11 --- I tested with 1.1.10 (current) and it did not crash. Can you retest?
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #7 from Robert Munteanu robert.munteanu@gmail.com 2008-12-16 01:27:53 --- Still crashes with 1.1.10 . I'll try a clean RTW install to see if that fixes anything.
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #8 from Austin English austinenglish@gmail.com 2009-06-16 14:23:56 --- Is this still an issue in current (1.1.23 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #9 from Robert Munteanu robert.munteanu@gmail.com 2009-06-17 08:27:09 --- (In reply to comment #8)
Is this still an issue in current (1.1.23 or newer) wine?
Yes checked with 1.1.23.
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #10 from Robert Munteanu robert.munteanu@gmail.com 2009-07-27 03:44:54 --- Still happens with 1.1.26
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #11 from Jeff Zaroyko jeffz@jeffz.name 2009-09-05 15:39:37 --- (In reply to comment #10)
Still happens with 1.1.26
Please attach a backtrace with debug symbols (either compile from source or install the dbg package) for wine 1.1.29. warn+all is just useless noise.
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #12 from Robert Munteanu robert.munteanu@gmail.com 2009-09-07 03:33:29 --- (In reply to comment #11)
(In reply to comment #10)
Still happens with 1.1.26
Please attach a backtrace with debug symbols (either compile from source or install the dbg package) for wine 1.1.29. warn+all is just useless noise.
This is what I got following the instructions at http://wiki.winehq.org/Backtraces:
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x7e7a1767). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:7e7a1767 ESP:00322b58 EBP:00322b80 EFLAGS:00210206( R- -- I - -P- ) EAX:7e795b50 EBX:7e7aeff4 ECX:13e375b0 EDX:00000000 ESI:00000000 EDI:13e375b0 Stack dump: 0x00322b58: 00000000 7e765a60 00322ba0 7e77fff4 0x00322b68: 13e377a0 13e375c8 00322b80 7e7aeff4 0x00322b78: 13e377a0 13e37778 00322bb0 7e7a06f7 0x00322b88: 13e375b0 00322be4 00000000 ffffffff 0x00322b98: 7e765a60 00322c38 00322bc0 7e77fff4 0x00322ba8: 13e377a0 13e375c8 00322bf0 7e69e708 Backtrace: =>0 0x7e7a1767 in d3d8 (+0x11767) (0x00322b80) 1 0x7e7a06f7 in d3d8 (+0x106f7) (0x00322bb0) 2 0x7e69e708 D3DCB_DefaultDestroySurface+0x78() in wined3d (0x00322bf0) 3 0x7e730f4b in wined3d (+0xe0f4b) (0x00322c20) 4 0x7e73222d texture_init+0x35d() in wined3d (0x00322c90) 5 0x7e695107 in wined3d (+0x45107) (0x00322cd0) 6 0x7e79c9e0 in d3d8 (+0xc9e0) (0x00322d20) 7 0x00ed3f2c in rometw (+0xad3f2c) (0x00322da0) 8 0x00ed4676 in rometw (+0xad4676) (0x00322e50) 9 0x00a32e19 in rometw (+0x632e19) (0x0ae12ef0) 10 0x0a050986 (0x0abeaeb0) 0x7e7a1767: movl 0x0(%edx),%ecx
Let me know if you need additional info.
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #13 from Jeff Zaroyko jeffz@jeffz.name 2009-09-07 03:59:03 --- (In reply to comment #12)
(In reply to comment #11)
(In reply to comment #10)
Still happens with 1.1.26
Please attach a backtrace with debug symbols (either compile from source or install the dbg package) for wine 1.1.29. warn+all is just useless noise.
This is what I got following the instructions at http://wiki.winehq.org/Backtraces:
useless spam Let me know if you need additional info.
Robert, please read instructions carefully, very clearly I wrote "attach a backtrace with debug symbols", not paste a backtrace without debug symbols. Pasting logs and ones that provide no additional information just make it more difficult to read the bug report.
The one you have pasted instead of attaching is missing debug symbols. You need to install debug symbols or compile from source.
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #14 from Robert Munteanu robert.munteanu@gmail.com 2009-09-07 04:04:36 ---
Robert, please read instructions carefully, very clearly I wrote "attach a backtrace with debug symbols", not paste a backtrace without debug symbols. Pasting logs and ones that provide no additional information just make it more difficult to read the bug report.
The one you have pasted instead of attaching is missing debug symbols. You need to install debug symbols or compile from source.
Jeff, first of all, I appreciate your patience.
Second of all, I have no idea how to create a backtrace with debug symbols. I have a wine-debuginfo package installed, after your first reply, which contains files like:
/usr/lib/debug/usr/lib/wine/d3drm.dll.so.debug /usr/lib/debug/.build-id/ad/d3fcb4573c67fce5bc1a5dc054f3a157bdd4b2.debug /usr/lib/debug/usr/bin/winecpp.debug
I followed the instructions at http://wiki.winehq.org/Backtraces and got the information I pasted in the comment above.
If there's a step I missed, please point me to the documentation or post instructions here and I'll be happy to follow them and update the wiki documentation.
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #15 from Jeff Zaroyko jeffz@jeffz.name 2009-09-07 04:41:04 --- (In reply to comment #14)
Second of all, I have no idea how to create a backtrace with debug symbols. I have a wine-debuginfo package installed, after your first reply, which contains files like:
/usr/lib/debug/usr/lib/wine/d3drm.dll.so.debug /usr/lib/debug/.build-id/ad/d3fcb4573c67fce5bc1a5dc054f3a157bdd4b2.debug /usr/lib/debug/usr/bin/winecpp.debug
I followed the instructions at http://wiki.winehq.org/Backtraces and got the information I pasted in the comment above.
If there's a step I missed, please point me to the documentation or post instructions here and I'll be happy to follow them and update the wiki documentation.
It could be that the debug symbols aren't complete, normally what you'd expect to see in a backtrace is the arguments to the function calls in the backtrace. Simplest thing to do would be to compile Wine from source, probably by getting a copy of the code from git and building that.
There is http://wiki.winehq.org/GitWine , http://wiki.winehq.org/WineOn64bit (if you're using a 64bit distro) and the README - if you need further help setting up / compiling, the forum is a good place to start rather than requesting further help here with the basics. Once you have that, you'll be able to provide much better bug reports.
http://bugs.winehq.org/show_bug.cgi?id=15496
--- Comment #16 from Robert Munteanu robert.munteanu@gmail.com 2009-09-22 04:44:45 --- I just upgraded by video card to a GeForce 8400 GS and the crash does not happen anymore so I won't be able to provide information in the future.
http://bugs.winehq.org/show_bug.cgi?id=15496
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #17 from joaopa jeremielapuree@yahoo.fr 2010-01-12 19:54:46 --- Surely a video driver bug, since changing the video card fixed the problem.
I think that this bug should be marked as INVALID.
http://bugs.winehq.org/show_bug.cgi?id=15496
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #18 from Jeff Zaroyko jeffz@jeffz.name 2010-01-12 20:01:57 --- (In reply to comment #17)
Surely a video driver bug, since changing the video card fixed the problem.
I think that this bug should be marked as INVALID.
Maybe a commit fixed the problem between the dates tested... the original crash was in d3d8 mind you. Marking fixed.
http://bugs.winehq.org/show_bug.cgi?id=15496
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #19 from Alexandre Julliard julliard@winehq.org 2010-01-22 11:01:53 --- Closing bugs fixed in 1.1.37.