Comment 72 for bug 1388612

(In reply to Ian Romanick from comment #68)
> 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?