<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - r600g: Diablo III Crashes After a few minutes" href="https://bugs.freedesktop.org/show_bug.cgi?id=74868#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - r600g: Diablo III Crashes After a few minutes" href="https://bugs.freedesktop.org/show_bug.cgi?id=74868">bug 74868</a> from <a class="email" href="mailto:nick.tenney@gmail.com" title="Nick Tenney <nick.tenney@gmail.com>"> Nick Tenney</a> <pre>(In reply to <a href="show_bug.cgi?id=74868#c14">comment #14</a>) > Created <a href="attachment.cgi?id=95909" name="attach_95909" title="r600g: Don't leak bytecode on shader compile failure">attachment 95909</a> <a href="attachment.cgi?id=95909&action=edit" title="r600g: Don't leak bytecode on shader compile failure">[details]</a> <a href='page.cgi?id=splinter.html&bug=74868&attachment=95909'>[review]</a> [review] > r600g: Don't leak bytecode on shader compile failure > > Does this patch help? Finally had a chance to test the patch. I compiled this morning with and without the patch and GALLIUM_HUD=fps,requested-VRAM,requested-GTT. It clearly leaked away without and the flow was stemmed with the proper error handling patch. Awesome! I see that the patch properly destroys the shader on error now, which is definitely an improvement. The error spamming to stdout is still occurring, so I'm not sure whether that should be another bug report/left open in this one with a new name or anything.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>