[Mesa-dev] [Bug 99055] Games hang / freeze completely

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Dec 11 15:31:56 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=99055

            Bug ID: 99055
           Summary: Games hang / freeze completely
           Product: Mesa
           Version: 13.0
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Other
          Assignee: mesa-dev at lists.freedesktop.org
          Reporter: etienne at bruines.com
        QA Contact: mesa-dev at lists.freedesktop.org

I recently updated to 13.0.2-1, and since then, any game will hang after about
a few minutes of gameplay (sometimes even less than a minute). I am not
entirely sure this is related to Mesa, but I'm confident that you'll be able to
point me in the right direction. 

Games tested: Factorio, Democracy 3. 
Things that do work: Google Chrome (Netflix / YouTube). 

-
  GL_VERSION:  3.0 Mesa 13.0.2
  GL_VENDOR:   Intel Open Source Technology Center
  GL_RENDERER: Mesa DRI Intel(R) Sandybridge Mobile x86/MMX/SSE2

-
No logs available at (looking around the moment of the 'hanging')
/var/log/syslog
/var/log/messages
/var/log/Xorg.0.log
dmesg

The games do not output anything either. The game just freezes, as if the
drawing-thread is hanging. Meaning after switching workspaces (screens), it'll
refuse to load anything new and show the "old workspace" at that location. 

At this stage I have no idea how to debug this. SIGINT won't stop the program,
I have to use SIGKILL. 

I have tried using `apitrace trace`. This "fixed" the bug: not able to
reproduce when using apitrace. The current workaround I'm using right now is
`apitrace trace -o /dev/null factorio` to start the game; it's a bit slower
because of the tracing, but it hasn't crashed so far. (It often looks like it's
going to crash, but it seems to recover from it)

I'd be happy to provide any additional information.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20161211/4d79b9a5/attachment-0001.html>


More information about the mesa-dev mailing list