<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [gen4] GPU Crash During Google Chrome Operation" href="https://bugs.freedesktop.org/show_bug.cgi?id=80568#c69">Comment # 69</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [gen4] GPU Crash During Google Chrome Operation" href="https://bugs.freedesktop.org/show_bug.cgi?id=80568">bug 80568</a> from <a class="email" href="mailto:alexsecret@hotmail.com" title="Alex <alexsecret@hotmail.com>"> Alex</a> <pre>(In reply to Ian Romanick from <a href="show_bug.cgi?id=80568#c68">comment #68</a>) > Another method is to set those options in either the user or system drirc. > I'm posting this from my phone, so I'll leave finding the details as an > exercise for the reader. :) First of all thank you for showing us this workaround. I read about drirc and found about driconf too and how we can set those options. Using this syntax though: "always_flush_cache=true always_flush_batch=true /usr/bin/google-chrome-stable & exit" runs chrome and closes the terminal right after and I guess this seems to be a better way to handle a temporary situation than changing dri settings and then changing them back to what they were when a fix is released. I'd like to ask what the drawbacks for these two settings are though. Are they slowing things down for the specific app that's using them for example?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>