From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 80419] XCOM: Enemy Unknown Causes lockup Date: Tue, 29 Dec 2015 20:17:39 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1038689291==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 6716C6E109 for ; Tue, 29 Dec 2015 12:17:39 -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 --===============1038689291== Content-Type: multipart/alternative; boundary="1451420259.D1dCdc2.5927"; charset="UTF-8" --1451420259.D1dCdc2.5927 Date: Tue, 29 Dec 2015 20:17:39 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D80419 Nicolai H=C3=A4hnle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nhaehnle@gmail.com --- Comment #93 from Nicolai H=C3=A4hnle --- Brief update: The crashes and Valgrind errors when playing back the trace a= re almost certainly unrelated to the lockup. It turns out apitrace is too aggressive in trimming the client-side memory blobs during recording. (See https://github.com/apitrace/apitrace/issues/407#issuecomment-167866502) On a more positive note, I am also seeing the lockup on Tonga from inside t= he game itself. Unfortunately, I cannot reproduce it reliably yet. --=20 You are receiving this mail because: You are the assignee for the bug. --1451420259.D1dCdc2.5927 Date: Tue, 29 Dec 2015 20:17:39 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Nicolai H=C3=A4hnle changed bug 80419<= /a>
What Removed Added
CC   nhaehnle@gmail.com

Commen= t # 93 on bug 80419<= /a> from Nicolai H=C3=A4hnle 
Brief update: The crashes and Valgrind errors when playing bac=
k the trace are
almost certainly unrelated to the lockup. It turns out apitrace is too
aggressive in trimming the client-side memory blobs during recording. (See
https://github.com/apitrace/apitrace/issues/407#issuecomment-167866=
502)

On a more positive note, I am also seeing the lockup on Tonga from inside t=
he
game itself. Unfortunately, I cannot reproduce it reliably yet.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1451420259.D1dCdc2.5927-- --===============1038689291== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1038689291==--