<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Dota 2 crashes sporadically on Intel/Mesa git (full backtrace with mesa symbols included)" href="https://bugs.freedesktop.org/show_bug.cgi?id=67120#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Dota 2 crashes sporadically on Intel/Mesa git (full backtrace with mesa symbols included)" href="https://bugs.freedesktop.org/show_bug.cgi?id=67120">bug 67120</a> from <a class="email" href="mailto:vrodic@gmail.com" title="Vedran Rodic <vrodic@gmail.com>"> Vedran Rodic</a> <pre>First I'll paste comment from Chris Forbes on the github issue: " Turns out this is the Jakiro crash as well. Warlock is a red herring; Jakiro does his Ice Path a little after 3:30 and the game crashes." ... "I've done a little bit of digging around -- it looks like the driver is behaving fine, and then when Ice Path is cast, something goes horribly wrong in shaderapidx9.so and it memcpy's junk over a bunch of internal mesa structures. Backtrace: <a href="http://sprunge.us/eeeH">http://sprunge.us/eeeH</a> " I've put a minimal .dem Dota 2 replay file here: <a href="http://mjesec.ffzg.hr/~vrodic/dota/jakiro-bug/">http://mjesec.ffzg.hr/~vrodic/dota/jakiro-bug/</a> If you put it in your "Steam/SteamApps/common/dota 2 beta/dota/replays" directory and then put the autoexec.cfg in directory in the url above to your "Steam/SteamApps/common/dota 2 beta/dota/cfg" directory, just starting Dota 2 and scrolling immediately to bottom left on minimap (so you can see Jakiro) when the game loads should trigger the crash. I've also recorded a trace of this using nouveau on my 9800 GT and though nouveau has problems displaying the game correctly at all, the trace file itself renders just fine on Intel/Mesa (latest version mentioned here), with everything shown as it should be, without triggering asserts. The trace of the replay (115MB bz2) will be uploaded to the same url above.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>