--- Comment #3 from Michel Dänzer <mic...@daenzer.net> ---
(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 CPU
profile of one of the other stalls.
Otherwise, maybe try setting the environment variable
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.
You are receiving this mail because:
You are the assignee for the bug.
mesa-dev mailing list