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: Sat, 23 Apr 2016 03:38:41 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1340787580==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2A7346E146 for ; Sat, 23 Apr 2016 03:38:41 +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 --===============1340787580== Content-Type: multipart/alternative; boundary="14613827211.5Fb24aeA.29407"; charset="UTF-8" --14613827211.5Fb24aeA.29407 Date: Sat, 23 Apr 2016 03:38:41 +0000 MIME-Version: 1.0 Content-Type: text/plain https://bugs.freedesktop.org/show_bug.cgi?id=94984 --- Comment #11 from Nicolai Hähnle --- This is an instance of the bug where we run into the kernel-imposed limit of 64K mmaps, see also bug 94726. They're not necessarily GL buffer objects, as internal buffers can contribute as well. In any case, this is non-trivial to fix. It seems like reducing the graphics quality might work around the problem in the meantime. There is also a potential workaround-patch attached to bug 94726, but it doesn't seem to actually work around the problem here. Thanks Edwin for giving me access to a live game where this bug occurs, and thanks Moritz for reporting the bug in the first place! -- You are receiving this mail because: You are the assignee for the bug. --14613827211.5Fb24aeA.29407 Date: Sat, 23 Apr 2016 03:38:41 +0000 MIME-Version: 1.0 Content-Type: text/html

Comment # 11 on bug 94984 from 
This is an instance of the bug where we run into the kernel-imposed limit of
64K mmaps, see also bug 94726. They're not necessarily GL buffer objects, as
internal buffers can contribute as well. In any case, this is non-trivial to
fix.

It seems like reducing the graphics quality might work around the problem in
the meantime. There is also a potential workaround-patch attached to bug 94726,
but it doesn't seem to actually work around the problem here.

Thanks Edwin for giving me access to a live game where this bug occurs, and
thanks Moritz for reporting the bug in the first place!

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