<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [amdgpu] Rocket League: long hangs (several seconds) when loading assets (models/textures/shaders?)" href="https://bugs.freedesktop.org/show_bug.cgi?id=97879#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [amdgpu] Rocket League: long hangs (several seconds) when loading assets (models/textures/shaders?)" href="https://bugs.freedesktop.org/show_bug.cgi?id=97879">bug 97879</a> from <a class="email" href="mailto:s.jegen@gmail.com" title="Silvan Jegen <s.jegen@gmail.com>"> Silvan Jegen</a> <pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=97879#c3">comment #3</a>) > (In reply to Silvan Jegen from <a href="show_bug.cgi?id=97879#c2">comment #2</a>) > > 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 > CPU profile of one of the other stalls. I tried to replay the trace and it crashed on my machine as well... > Otherwise, maybe try setting the environment variable > GALLIUM_HUD=.dfps,requested-VRAM+VRAM-usage,requested-GTT+GTT-usage, > cpu+temperature+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 allow at least confirming or ruling out that > the other stalls are due to shader compilation as well. Do you still need such a screenshot now that other people in the thread have posted a few? If so, I will upload one early next week (I will be away over the weekend).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>