http://bugs.winehq.org/show_bug.cgi?id=27520
Summary: Rift: opengl crash with latest git (20110617) Product: Wine Version: unspecified Platform: x86-64 OS/Version: Mac OS X 10.6 Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: timwoj@ieee.org
Created an attachment (id=35187) --> (http://bugs.winehq.org/attachment.cgi?id=35187) Full crash log
I just updated to the latest git, and Rift crashes at startup now. The launcher starts but as soon as I press play it flashes the whole screen white and then dumps me into the crash reporter. The full log is attached.
http://bugs.winehq.org/show_bug.cgi?id=27520
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |1.3.22 Summary|Rift: opengl crash with |Rift crashes |latest git (20110617) |
--- Comment #1 from Jeff Zaroyko jeffz@jeffz.name 2011-06-17 23:24:22 CDT --- Please perform a regression test http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=27520
--- Comment #2 from Tim Wojtulewicz timwoj@ieee.org 2011-06-23 21:48:56 CDT --- I ran a regression test and was unable to pin-point a spot in the git tree where it stopped working. This is likely a bug with Rift itself, since it was working in the early 1.2.x revisions (of Rift), and stopped working right before 1.3 was released. Since there's no way to patch back to a prior version of Rift, I'm not sure where to go from here.
http://bugs.winehq.org/show_bug.cgi?id=27520
--- Comment #3 from Jeff Zaroyko jeffz@jeffz.name 2011-06-23 22:17:53 CDT --- Since it uses a crash handler there is no backtrace in your crash log. See if you can produce one using winedbg http://wiki.winehq.org/Backtraces
http://bugs.winehq.org/show_bug.cgi?id=27520
--- Comment #4 from Tim Wojtulewicz timwoj@ieee.org 2011-06-23 22:45:07 CDT --- Created an attachment (id=35258) --> (http://bugs.winehq.org/attachment.cgi?id=35258) Backtrace of crash.
Rift has an error handler that pops up to send crash information back to Trion. I'm not sure if this backtrace occurs before or after that.
http://bugs.winehq.org/show_bug.cgi?id=27520
John Stahara john.stahara+winehq@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |john.stahara+winehq@gmail.c | |om
--- Comment #5 from John Stahara john.stahara+winehq@gmail.com 2011-06-26 10:14:23 CDT --- (In reply to comment #4)
Created an attachment (id=35258)
--> (http://bugs.winehq.org/attachment.cgi?id=35258) [details]
Backtrace of crash.
Rift has an error handler that pops up to send crash information back to Trion. I'm not sure if this backtrace occurs before or after that.
The error handler process runs in the background when the game starts; its presence in the list doesn't necessarily indicate that its error-reporting functionality has been triggered. The useful traces are those that would come from rift.exe, but those are the processes that cannot be attached (the "error 5" ones).
http://bugs.winehq.org/show_bug.cgi?id=27520
--- Comment #6 from Tim Wojtulewicz timwoj@ieee.org 2011-06-29 11:24:01 CDT ---
From the Rift 1.3 Hotfix #3 patch notes (released today):
CLIENT/SERVER
Fixed an issue preventing the game from starting properly when running Wine.
I'll test this when I get home, but this bug report can likely be closed.
http://bugs.winehq.org/show_bug.cgi?id=27520
--- Comment #7 from Michael Bond mikejbond@gmail.com 2011-06-29 14:39:03 CDT --- Created an attachment (id=35355) --> (http://bugs.winehq.org/attachment.cgi?id=35355) RIFT 1.3 with wine-git
Updated RIFT to 1.3 and have tried both wine 1.3.23 and git and unable to launch the actual game. Pressing play in the patcher appears to attempt to launch but the game appears to fail to launch. Attached is a log including three attempts to launch the actual game from the patcher using wine-git. The first attempt generated the err:seh:setup_exception_record line in the log.
http://bugs.winehq.org/show_bug.cgi?id=27520
Michael Bond mikejbond@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mikejbond@gmail.com
--- Comment #8 from Michael Bond mikejbond@gmail.com 2011-06-29 14:40:34 CDT --- The previous comment it should have stated RIFT 1.3 Hotfix #4.
http://bugs.winehq.org/show_bug.cgi?id=27520
--- Comment #9 from Tim Wojtulewicz timwoj@ieee.org 2011-06-29 19:26:54 CDT --- I can confirm that it's still broken with the latest 1.3 patch (hotfix #4). Previously I could press Play on the launcher and it would start the game before crashing while loading. Now when I press Play, Wine spits out that stack overflow error (as Michael posted) and does nothing. My values from the error are slightly different, but likely the same issue.
http://bugs.winehq.org/show_bug.cgi?id=27520
--- Comment #10 from Mario Moritz eSsMario.home@googlemail.com 2011-07-02 08:55:14 CDT --- Created an attachment (id=35401) --> (http://bugs.winehq.org/attachment.cgi?id=35401) console output Rift 1.3 Hotfix 6
I have the same Problem test with wine 1.2.23
the prefix isn't clean privios installed games: settlers 3 gold, patician 2 gold, world of warcraft: catalysm
The game starts with fickering video audio works, but the screen shows only bright areas.
http://bugs.winehq.org/show_bug.cgi?id=27520
--- Comment #11 from Tim Wojtulewicz timwoj@ieee.org 2011-07-14 22:30:15 CDT --- Created an attachment (id=35550) --> (http://bugs.winehq.org/attachment.cgi?id=35550) Rift crashing to a Wine crash window
A small change on this since I last posted. I've updated to the latest git and changed my configuration from Windows XP to Windows 7. Now instead of getting the Rift crash logger, I get a Wine window that says it crashed. I still can't attach a debugger. Even after it crashes, if I drop into winedbg it says it can't attach to the process. I've attached the relevant part of the Wine log when it crashes.
http://bugs.winehq.org/show_bug.cgi?id=27520
Tim Wojtulewicz timwoj@ieee.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #35187|0 |1 is obsolete| | Attachment #35258|0 |1 is obsolete| |
--- Comment #12 from Tim Wojtulewicz timwoj@ieee.org 2011-07-24 21:26:25 CDT --- Created an attachment (id=35683) --> (http://bugs.winehq.org/attachment.cgi?id=35683) Real backtrace
I finally got a true backtrace of this crashing. I had to kill the rift error handling process that was blocking winedbg from letting me attach to rift.
http://bugs.winehq.org/show_bug.cgi?id=27520
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh@gmail.com
--- Comment #13 from Jerome Leclanche adys.wh@gmail.com 2011-07-24 21:35:31 CDT --- (In reply to comment #12) Please install or compile-in debug symbols.
http://bugs.winehq.org/show_bug.cgi?id=27520
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- OS/Version|Mac OS X 10.6 |Mac OS X
http://bugs.winehq.org/show_bug.cgi?id=27520
Tim Wojtulewicz timwoj@ieee.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #14 from Tim Wojtulewicz timwoj@ieee.org 2011-11-07 22:14:19 CST --- I have Rift working under Wineskin in OS X, so I'm going to mark this bug as invalid. It was apparently just a compilation issue of some sort on my end. Sorry for the noise.
http://bugs.winehq.org/show_bug.cgi?id=27520
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #15 from Jerome Leclanche adys.wh@gmail.com 2011-11-08 09:28:56 CST --- Closing
-
wine-bugs＠winehq.org