[Bug 22212] New: Random Crashes in Sacred 2

http://bugs.winehq.org/show_bug.cgi?id=22212

Summary: Random Crashes in Sacred 2
           Product: Wine
           Version: 1.1.41
          Platform: x86-64
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

When playing sacred 2. from time to time wine crashes (sometimes in game
(singleplayer and LAN), sometimes in the menu). It does not happen too often,
but it is still annoying.
I am using Wine 1.1.41. on Ubuntu Lucid.

I am starting the game like this:
WINEPREFIX=~/.wine/sacred2 wine sacred2.exe

WINEDEBUG=+relay wouldn't work, but I hope you can get some stuff out of the
logfile anyway. If you can help me getting it to start with +relay, I will be
happy to post the log.

[Bug 22212] Random Crashes in Sacred 2

http://bugs.winehq.org/show_bug.cgi?id=22212

--- Comment #1 from Woula Dingdong   2010-03-30 15:10:40 ---
(When I execute 'WINEDEBUG=+relay WINEPREFIX=~/.wine/sacred2 wine sacred2.exe'
the game won't run, but my terminal is spammed with debug information. Any way
to cut the debug messages shorter, but still get the needed information?

[Bug 22212] Random Crashes in Sacred 2

http://bugs.winehq.org/show_bug.cgi?id=22212

--- Comment #2 from Juan Lang   2010-03-30 15:18:04 ---
That's not spam, that's what WINEDEBUG=+relay does.  Redirect it to a file.
http://wiki.winehq.org/FAQ#get_log

[Bug 22212] Random Crashes in Sacred 2

http://bugs.winehq.org/show_bug.cgi?id=22212

--- Comment #3 from Woula Dingdong   2010-03-30 16:38:26 ---
The problem is not getting the debug information into a file, but running the
game while debugging. Using 'WINEDEBUG=+relay' makes it take ages to load, and
then finally the games say 'gameserver:timeout' at the end of the startup and
exits itself. I tried 'WINEPREFIX=~/.wine/sacred2 WINEDEBUG=+relay,+seh,+tid
wine sacred2.exe &> /tmp/output.txt' like in the FAQ... I cancelled it after 10
minutes or so and output.txt turned out to be 2.5 GB big o.O. Do I do something
wrong? Is there any way to cut the debug information shorter?

[Bug 22212] Random Crashes in Sacred 2

http://bugs.winehq.org/show_bug.cgi?id=22212

--- Comment #4 from Juan Lang   2010-03-30 17:08:52 ---
Yes, +relay slows things down considerably.

Actually, you've never attached a log without +relay.  Attach one of those
first.

[Bug 22212] Random Crashes in Sacred 2

http://bugs.winehq.org/show_bug.cgi?id=22212

--- Comment #5 from Woula Dingdong   2010-03-30 18:38:22 ---
Created an attachment (id=27109)
 --> (http://bugs.winehq.org/attachment.cgi?id=27109)
Output from $ WINEPREFIX=~/.wine/sacred2 wine sacred2.exe &>
~/.wine/sacred2-log

Oh, I didn't it work the first time? Whatever, heres another one. I had to kill
the app (CTRL+C) after the crash, didn't react on me clicking the exit-button.

[Bug 22212] Random Crashes in Sacred 2

http://bugs.winehq.org/show_bug.cgi?id=22212

Patrick Trentin  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
                   |                            |m

[Bug 22212] Random Crashes in Sacred 2

http://bugs.winehq.org/show_bug.cgi?id=22212

Dan Kegel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #6 from Dan Kegel  2010-12-01 11:57:19 CST ---
The log ends with
wine: Unhandled page fault on write access to 0x00000004 at address 0x7e0b6af1
(thread 0009), starting debugger...
but lacks the backtrace that should follow.  Perhaps you didn't click
the button on the crash dialog?

But 1.1.41 is pretty old.  Please try wine-1.3.8 from winehq.org,
the problem may have been fixed already.

If it still crashes, please send the log again, and this time either 
click the button on the crash dialog, or do 'winetricks nocrashdialog' first.
Also, just attach small logs as uncompressed text files with names ending in
.txt, that makes it easier to get to.
Thanks!

[Bug 22212] Random Crashes in Sacred 2

http://bugs.winehq.org/show_bug.cgi?id=22212

--- Comment #7 from Dan Kegel  2010-12-01 11:58:26 CST ---
Also, what graphics card and driver?

[Bug 22212] Random Crashes in Sacred 2

http://bugs.winehq.org/show_bug.cgi?id=22212

Xavier Vachon  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #8 from Xavier Vachon  2011-04-08 01:21:31 CDT ---
In git, I have been able to play Sacred 2 2.65.1 for about an hour, with no
crashes. I used overrides vcrun2005 and d3dx9_36 to work around bugs 25364 -
25365 - 25366. Graphics settings are Elite textures, all settings to
high/very-high, no PhysX and Anti-aliasing.

Gentoo Linux X64
GeForce 8800GT - nvidia-drivers-270.30

[Bug 22212] Random Crashes in Sacred 2

http://bugs.winehq.org/show_bug.cgi?id=22212

Dan Kegel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |ABANDONED

--- Comment #9 from Dan Kegel  2011-04-08 08:54:38 CDT ---
No response in a year, reported working -> fixed or abandoned.
Fickle finger of fate says... abandoned, since we don't know what graphics card
original poster used.

[Bug 22212] Random Crashes in Sacred 2

http://bugs.winehq.org/show_bug.cgi?id=22212

Dmitry Timoshkov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #10 from Dmitry Timoshkov  2011-04-08 22:27:03 CDT ---
Closing abandoned.