[Bug 103810] Team Fortress 2 HDR Enabled Crashes

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Nov 19 00:05:44 UTC 2017


            Bug ID: 103810
           Summary: Team Fortress 2 HDR Enabled Crashes
           Product: Mesa
           Version: 17.2
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/i965
          Assignee: intel-3d-bugs at lists.freedesktop.org
          Reporter: frail.knight at gmail.com
        QA Contact: intel-3d-bugs at lists.freedesktop.org

Created attachment 135580
  --> https://bugs.freedesktop.org/attachment.cgi?id=135580&action=edit
Console.log showing a few runs, crashes and alternate VAC complaints from
switching HDR option

In Team Fortress 2 if I set High Dynamic Range option to Bloom (If available),
I get the following errors.  These are from 3 separate crashes, all immediately
after entering a server and attempting to choose a class at the class loadout
screen, or within seconds of starting play.

MatQueue0[16918]: segfault at 8 ip 00000000f51e49e8 sp 0000000004556ed0 error 4
in i965_dri.so[f4de6000+8d4000]

hl2_linux[17355]: segfault at 0 ip 00000000f51fa929 sp 00000000ffcda660 error 6
in i965_dri.so[f4e0e000+8d4000]

MatQueue0[18870]: segfault at 0 ip 00000000f7e39dcc sp 00000000009169d8 error 6
in libc-2.26.so[f7cfd000+1cf000]

These crashes stop if I set the High Dynamic Range option to None.  However,
when I do set the value of HDR to None, VAC swears I've modified my game files
for some strange reason.  If I set HDR back to Bloom (If available), suddenly
I'm ok and can connect to servers again without VAC complaining...But then it
crashes.  I will post this in Valve's Git as well because I'm torn between this
being a Mesa issue and a Valve issue.

Note:  I've also seen:  https://bugs.freedesktop.org/show_bug.cgi?id=101443
BUT per Comment #3, that user states his crashes occur with HDR disabled, and
he is using an older version of Mesa (17.1.2).  I see the issue with Bloom
enabled, and I'm using Mesa 17.2.2

You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20171119/ecf7ccae/attachment.html>

More information about the intel-3d-bugs mailing list