http://bugs.winehq.org/show_bug.cgi?id=19991
Summary: Battlefield Heroes: crash immediately after level load Product: Wine Version: 1.1.29 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: roothorick@new.rr.com
Created an attachment (id=23517) --> (http://bugs.winehq.org/attachment.cgi?id=23517) wine output.
Install per details on AppDB entry, run, pick character, PLAY NOW. The game loads, your character spawns, and the immediate frame after: "This program has encountered a serious problem and needs to close." The "Close" button is unclickable, too, leaving me to ^C it and never get a backtrace. With some trickiness to get around the anti-debugger voodoo, I managed to get a backtrace by attaching winedbg seconds before the crash happens. Will be second attachment.
In the log I did NOT attach, and ^C immediately after the crash.
If it helps any: Radeon HD 4850, Catalyst 9.8. Gentoo amd64.
http://bugs.winehq.org/show_bug.cgi?id=19991
--- Comment #1 from Ben Anderson roothorick@new.rr.com 2009-09-09 00:14:07 --- Created an attachment (id=23518) --> (http://bugs.winehq.org/attachment.cgi?id=23518) Backtrace from winedbg
http://bugs.winehq.org/show_bug.cgi?id=19991
--- Comment #2 from Jeff Zaroyko jeffz@jeffz.name 2009-09-09 00:16:47 --- Is this a regression? http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=19991
--- Comment #3 from Ben Anderson roothorick@new.rr.com 2009-09-09 00:19:36 --- I installed 1.1.28 just to check, as someone was reporting punkbuster kicking with 1.1.28 in appdb. The same crash happened there too. It's far more likely that DICE in a recent update added something that doesn't play nice with Wine.
http://bugs.winehq.org/show_bug.cgi?id=19991
--- Comment #4 from Jeff Zaroyko jeffz@jeffz.name 2009-09-09 00:24:17 --- (In reply to comment #3)
I installed 1.1.28 just to check, as someone was reporting punkbuster kicking with 1.1.28 in appdb. The same crash happened there too. It's far more likely that DICE in a recent update added something that doesn't play nice with Wine.
That's possible, the last version I tested was a few months ago when it worked for me.
http://bugs.winehq.org/show_bug.cgi?id=19991
--- Comment #5 from Austin English austinenglish@gmail.com 2011-10-01 15:10:05 CDT --- This is your friendly reminder that there has been no bug activity for 1 year. Is this still an issue in current (1.3.29 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=19991
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |ABANDONED
--- Comment #6 from Austin English austinenglish@gmail.com 2013-11-13 15:38:50 CST --- No reply in over a year, and no download. Resolving abandoned, if anyone is still able to reproduce this in the current development version (currently 1.7.6) feel free to reopen.
http://bugs.winehq.org/show_bug.cgi?id=19991
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Austin English austinenglish@gmail.com 2013-11-13 15:40:35 CST --- Closing.
-
wine-bugs＠winehq.org