Comment 10 for bug 2020604

While it's obviously not a real fix, As I don't use chrome as my primary browser, simply regenerating my ~/.config/google-chrome/ directory resolved this issue. Others may not have this option.

Question 1 : What is it about the Mesa upgrade that kills chrome but not Firefox?
Question 2 : Is there a less nuclear fix than wiping the Chrome settings? e.g. Deleting just the ShaderCache or GrShaderCache directories?