From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 80419] XCOM: Enemy Unknown Causes lockup
Date: Fri, 05 Feb 2016 14:14:07 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1816654809=="
Return-path:
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id F10216EA01
for ; Fri, 5 Feb 2016 06:14:07 -0800 (PST)
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
--===============1816654809==
Content-Type: multipart/alternative; boundary="145468164715.8dd4c.10346";
charset="UTF-8"
--145468164715.8dd4c.10346
Date: Fri, 5 Feb 2016 14:14:07 +0000
MIME-Version: 1.0
Content-Type: text/plain
https://bugs.freedesktop.org/show_bug.cgi?id=80419
--- Comment #111 from Nicolai Hähnle ---
The apitrace-related crash from those earlier comments is not an XCOM bug.
However, if I recall correctly, XCOM issues DrawRangeElements calls with ranges
that are larger than necessary. This hurts performance slightly when vertex
data is not in VBOs; it is irrelevant when all vertex data is in VBOs.
I have been able to reproduce the lockup (thanks to Edwin), but it takes a
fairly long time inside the game to happen for me. With everything else that is
going on, I simple haven't yet had the time to collect enough information to
really understand what's going on.
--
You are receiving this mail because:
You are the assignee for the bug.
--145468164715.8dd4c.10346
Date: Fri, 5 Feb 2016 14:14:07 +0000
MIME-Version: 1.0
Content-Type: text/html
Comment # 111
on bug 80419
from Nicolai Hähnle
The apitrace-related crash from those earlier comments is not an XCOM bug.
However, if I recall correctly, XCOM issues DrawRangeElements calls with ranges
that are larger than necessary. This hurts performance slightly when vertex
data is not in VBOs; it is irrelevant when all vertex data is in VBOs.
I have been able to reproduce the lockup (thanks to Edwin), but it takes a
fairly long time inside the game to happen for me. With everything else that is
going on, I simple haven't yet had the time to collect enough information to
really understand what's going on.
You are receiving this mail because:
- You are the assignee for the bug.
--145468164715.8dd4c.10346--
--===============1816654809==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0
cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK
--===============1816654809==--