Summary: | Assertion failure in radeon_drm_cs.c (Shadow of Mordor) | ||
---|---|---|---|
Product: | Mesa | Reporter: | Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0x9b> |
Component: | Drivers/Gallium/radeonsi | Assignee: | Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0x9b> |
Status: | RESOLVED WORKSFORME | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | minor | ||
Priority: | medium | CC: | 0xe2.0x9a.0x9b |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Jan Ziak (http://atom-symbol.net)
2016-06-02 16:24:02 UTC
Is this a regression? If yes, can you bisect? This is a data race issue caused by incorrect locking of gl_context by the game. The game is indirectly using the same gl_context from two OS threads. I take it this means this can be closed as NOTOURBUG? (In reply to Nicolai Hähnle from comment #3) > I take it this means this can be closed as NOTOURBUG? If it was my decision to make, I would still fix it in Mesa because it slightly broadens the range of stable applications and slightly increases end-user satisfaction. Programming bugs cannot be prevented in an absolute sense. If possible Mesa should print a warning with backtraces (libunwind?) which would help application developers to locate the problem. I suggest to leave this bug open. A Feral representative told me that Shadow Of Mordor works. (In reply to Marek Olšák from comment #5) > A Feral representative told me that Shadow Of Mordor works. Just a note: I protect a number of OpenGL API functions by a mutex added via a private patch to my local Mesa installation, so Shadow of Mordor works OK on my machine. Prior to that, I was experiencing failures in this game, mostly in the game menu. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.