From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 94984] XCom2 crashes with SIGSEGV on radeonsi Date: Mon, 25 Apr 2016 08:30:06 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1561287318==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id CA7996E525 for ; Mon, 25 Apr 2016 08:30:06 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1561287318== Content-Type: multipart/alternative; boundary="14615730061.0F04B8.18602"; charset="UTF-8" --14615730061.0F04B8.18602 Date: Mon, 25 Apr 2016 08:30:06 +0000 MIME-Version: 1.0 Content-Type: text/plain https://bugs.freedesktop.org/show_bug.cgi?id=94984 --- Comment #12 from Edwin Smith (Feral Interactive) --- Although XCOM 2 isn't supported on Mesa right now we'll see if we can get the game to limit the number of buffer objects it is using if it notices the system is getting close to the 64k limit as explained by Nicolai. We don't know how feasible this will be and the impact it will have on performance of XCOM 2 but given the driver side fix is none trivial we'll see if we can at least guard against the issue and avoid the user experiencing a SIGSEGV. -- You are receiving this mail because: You are the assignee for the bug. --14615730061.0F04B8.18602 Date: Mon, 25 Apr 2016 08:30:06 +0000 MIME-Version: 1.0 Content-Type: text/html

Comment # 12 on bug 94984 from 
Although XCOM 2 isn't supported on Mesa right now we'll see if we can get the
game to limit the number of buffer objects it is using if it notices the system
is getting close to the 64k limit as explained by Nicolai. 

We don't know how feasible this will be and the impact it will have on
performance of XCOM 2 but given the driver side fix is none trivial we'll see
if we can at least guard against the issue and avoid the user experiencing a
SIGSEGV.

You are receiving this mail because:
  • You are the assignee for the bug.
--14615730061.0F04B8.18602-- --===============1561287318== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1561287318==--