From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 97879] [amdgpu] Rocket League: long hangs (several seconds) when loading assets (models/textures/shaders?) Date: Wed, 21 Sep 2016 14:59:41 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1970525451==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 82DF86E846 for ; Wed, 21 Sep 2016 14:59: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 --===============1970525451== Content-Type: multipart/alternative; boundary="14744699811.5B051c.20054"; charset="UTF-8" --14744699811.5B051c.20054 Date: Wed, 21 Sep 2016 14:59:41 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D97879 --- Comment #3 from Michel D=C3=A4nzer --- (In reply to Silvan Jegen from comment #2) > Just to clarify: the trace also includes loading of the game itself (which > takes a long time too) as well as in-game menu navigation. Right, replaying the trace crashes for me after the shader compilations on startup, so my CPU profile only covered that. Maybe you can try getting a C= PU profile of one of the other stalls. Otherwise, maybe try setting the environment variable GALLIUM_HUD=3D.dfps,requested-VRAM+VRAM-usage,requested-GTT+GTT-usage,cpu+t= emperature+GPU-load,.dnum-bytes-moved,.dbuffer-wait-time,.dnum-compilations= +num-shaders-created for either running the game itself or replaying the trace, and taking a screenshot within one minute after one of the other stalls. That should all= ow at least confirming or ruling out that the other stalls are due to shader compilation as well. --=20 You are receiving this mail because: You are on the CC list for the bug.= --14744699811.5B051c.20054 Date: Wed, 21 Sep 2016 14:59:41 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comment= # 3 on bug 97879<= /a> from Michel D=C3=A4nzer 
(In reply to Silvan Jegen from comment #2)
> Just to clarify: the trace also includes loading=
 of the game itself (which
> takes a long time too) as well as in-game menu navigation.

Right, replaying the trace crashes for me after the shader compilations on
startup, so my CPU profile only covered that. Maybe you can try getting a C=
PU
profile of one of the other stalls.

Otherwise, maybe try setting the environment variable
GALLIUM_HUD=3D.dfps,requested-VRAM+VRAM-usage,requested-GTT+GTT-usage,cpu+t=
emperature+GPU-load,.dnum-bytes-moved,.dbuffer-wait-time,.dnum-compilations=
+num-shaders-created
for either running the game itself or replaying the trace, and taking a
screenshot within one minute after one of the other stalls. That should all=
ow
at least confirming or ruling out that the other stalls are due to shader
compilation as well.

You are receiving this mail because:
  • You are on the CC list for the bug.
= --14744699811.5B051c.20054-- --===============1970525451== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1970525451==--