[Bug 111339] [Debug mesa]. Dirt 4 crashes after launching

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Sep 6 17:19:55 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=111339

--- Comment #15 from Jason Ekstrand <jason at jlekstrand.net> ---
I(In reply to leozinho29_eu from comment #12)
> And searching in the internet wasn't fruitful. Tried many things, some just
> ignored valgrind, others made the game end in an infinite loop before the
> launch screen opens. What is the correct procedure? Opening DiRT 4 without
> Steam isn't useful, as it uses different libraries causing unrelated crashes
> in different moments. This crash happens using Steam and happens just before
> or just after the stage scenario finishes loading.

I wouldn't waste time trying to get the app to run under valgrind.  Between
wine and the game, you're likely to see piles of valgrind errors and trying to
find the mesa issue will be near impossible.  One thing to try would be to
capture the pipelines with fossilize
(https://github.com/ValveSoftware/Fossilize) and then run valgrind on a
fossilize replay.  If you can repro with a fossilize replay, it also makes
debugging way easier because you can use normal GDB instead of the wine
version.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20190906/11117f7a/attachment.html>


More information about the intel-3d-bugs mailing list