<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - radeonsi minecraft forge splash freeze since 17.1" href="https://bugs.freedesktop.org/show_bug.cgi?id=101294#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - radeonsi minecraft forge splash freeze since 17.1" href="https://bugs.freedesktop.org/show_bug.cgi?id=101294">bug 101294</a> from <a class="email" href="mailto:sonichedgehog_hyperblast00@yahoo.com" title="MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com>"> MirceaKitsune</a> <pre>Greetings. I'm also getting a GPU crash / system lockup, when running Minecraft as well as other game engines. It doesn't happen during the splash screen, but probabilistically while the game is running. The problem was introduced at the same date as the making of this report, also around the time my distribution upgraded to Mesa 17.1. I assume I'm experiencing the same bug described here, since I honestly don't see Mesa 17.1 introducing two completely unrelated crashes that would cause a renderer as simple as Minecraft to crash the OS. However I updated to Mesa 17.1.4, and surprisingly it still occurs. Therefore it's possible that this was not fixed. Since it's not my bug and I don't wish to inconvenience folks, I won't set the status to reopened... however the developers might wish to take a look at this. Here is my own report: <a class="bz_bug_link bz_status_NEW " title="NEW - radeonsi: 3D engines causing frequent GPU lockups" href="show_bug.cgi?id=101672">https://bugs.freedesktop.org/show_bug.cgi?id=101672</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>