https://bugs.winehq.org/show_bug.cgi?id=42098
Bug ID: 42098 Summary: Bioshock crashes on i965 during gameplay Product: Wine Version: 2.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dandart@googlemail.com Distribution: ---
Created attachment 56613 --> https://bugs.winehq.org/attachment.cgi?id=56613 Backtrace (i915 related)
I think this may be due to another i965 freedesktop bug but in case it isn't I've attached a backtrace of the crash report received under wine, which references i915 dri.
Relevant specs: Intel HD (Skylake 6200u, i965) on Ubuntu 16.04 (well, Mint 18 anyway) using the latest ppa:oibaf/graphics-drivers (giving me OpenGL 4.5 support).
The specific point the game crashes is after the loading sign upon entering the city - I thought it could be due to insufficient graphics memory or something.
Cheers
https://bugs.winehq.org/show_bug.cgi?id=42098
--- Comment #1 from Dan Dart dandart@googlemail.com --- Realised this was the csmt version - so trying again without!
https://bugs.winehq.org/show_bug.cgi?id=42098
Dan Dart dandart@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Bioshock crashes on i965 |[CSMT] Bioshock crashes on |during gameplay |i965 during gameplay
https://bugs.winehq.org/show_bug.cgi?id=42098
Kathie Dart winehq@kathiedart.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|[CSMT] Bioshock crashes on |Bioshock crashes on i965 |i965 during gameplay |during gameplay
https://bugs.winehq.org/show_bug.cgi?id=42098
--- Comment #2 from Kathie Dart winehq@kathiedart.uk --- Created attachment 56614 --> https://bugs.winehq.org/attachment.cgi?id=56614 Non-CSMT equivalent backtrace
Here's an equivalent backtrace with CSMT turned off.
https://bugs.winehq.org/show_bug.cgi?id=42098
--- Comment #3 from Matteo Bruni matteo.mystral@gmail.com --- This might also have to do with running out of addressing space. Something like bug 34658 comment 9 might help here.
If it doesn't help, can you attach the full, plain terminal output associated with a crash?
https://bugs.winehq.org/show_bug.cgi?id=42098
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #4 from joaopa jeremielapuree@yahoo.fr --- No news from the OP since 3 years. No download available Can an administrator close this bug as FIXED?
https://bugs.winehq.org/show_bug.cgi?id=42098
--- Comment #5 from joaopa jeremielapuree@yahoo.fr --- aarrgghhh. As ABANDONED I meant
https://bugs.winehq.org/show_bug.cgi?id=42098
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #6 from Jeff Zaroyko jeffz@jeffz.name --- Marking abandoned. No response from reporter.
https://bugs.winehq.org/show_bug.cgi?id=42098
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de Status|RESOLVED |CLOSED
--- Comment #7 from André H. nerv@dawncrow.de --- closing abandoned
-
wine-bugs＠winehq.org -
WineHQ Bugzilla