Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
mesa
mesa
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 1,902
    • Issues 1,902
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 314
    • Merge Requests 314
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Packages
    • Packages
    • Container Registry
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Mesa
  • mesamesa
  • Issues
  • #1284

Closed
Open
Opened Sep 25, 2019 by Bugzilla Migration User@bugzilla-migration
  • Report abuse
  • New issue
Report abuse New issue

GPU crash running Overwatch in wine-staging

Submitted by Tobias Auerochs

Assigned to Default DRI bug account

Link to original bug (#102962)

Description

Running Overwatch in wine-staging 2.17 or 2.16 causes frequent GPU crashes, in particular almost always when selecting Symmetra in the Hero Selection screen. As far as I can tell there is no version of wine-staging (including specific commits) that avoid this issue.

Interestingly, a patched version of wine-staging 2.16 and earlier (https://github.com/gamax92/wine-overwatch) does not seem to trigger this at all. (I suspect their removal of some wined3d related patches started to trigger this, whilst the earlier version avoided it.)

No errors are shown on both wine's and mesa's end, although I have not successfully tried a build with -DDEBUG CFLAG, which I could try in case this is helpful.

I have tried working out which of the patches applied by the repository are avoiding the issue, but haven't work out any good leads.

Running on Arch Linux with linux 4.13.3 (Custom compiled with unrelated patches) and mesa 17.2.1. The issue can be reproduced both with the standard wine-staging package on Arch as well as compiling the mentioned patched version.

It might be worthwile to contact the wine developers about this, but their bug reporting guidelines specifically say to not report driver issues there, so I decided to report here first.

Version: 17.2

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
3
Labels
bugzilla Needs Information radeonsi
Assign labels
  • View project labels
Reference: mesa/mesa#1284