Rats Webgl Hit A Snag Chrome Fix

Have you had this problem: “Rats! WebGL hit a snag.” Usually, you get this message in the error bar on Google Chrome. So what is it all about? Before we tell you about it, let’s understand a little about WebGL.

WebGL or Web Graphics Library is a JavaScript API that helps with rendering interactive 3D computer graphics and 2D graphics on any compatible web browser, without requiring the use of plug-ins.

It enables GPU accelerated image processing and the use of physics. WebGL programs consist of code written in JavaScript and are executed on the computer’s GPU or Graphics Processing Unit.

The non-profit, Khronos Group designs and maintains WebGL.

WebGL works as a thin wrapper around OpenGL. OpenGL is a low level library used for drawing 2D graphics. Basically, OpenGL gives us the ability to push data to the GPU, and then to execute specialized code on the GPU itself rather than on the CPU.

WebGL helps to optimize the performance of browsers, JavaScript and graphics drivers when it comes to 2D and 3D graphics. In fact, WebGL is the best way to bring 3D everywhere. It allows you to write once, run everywhere.

When using WebGL, you may have had a problem with a site falling back to canvas rendering if WebGL is not supported or is found to have an error. When using WebGL in Google Chrome, an error message bar appears – “Rats! WebGL hit a snag.” It does not disappear till you do something about it.

Rats Webgl Hit A Snag Error

Rats Webgl Hit A Snag Error

If you try reloading the page or navigating to a different one, the message reappears the next time you use WebGL. In fact, you get the error message every time a web page tries to access WebGL. And once the error occurs, Chrome will not use WebGL on the same site again, until and unless you specifically reload it.

So, the “Rats! WebGL hit a snag” message does not indicate continuous errors, but just that you have been making continuous attempts to use WebGL.

You can fix the problem and solve your page rendering issues by disabling hardware accelerated graphics from the settings in Google Chrome.

How to Disable Hardware Accelerated Graphics In Chrome:

  1. chrome://settings -> Show advanced settings.
  2. Here, you will find an option “Use hardware acceleration when available”.
  3. Just uncheck it and restart the browser. This should solve the problem.

Another option is to go to chrome://flags. Here you will get an option, “Disable WebGL”. Click the checkbox next to that, and restart the browser.

The two methods given here are simple and work well to get rid of the error message, “Rats! WebGL hit a snag” on your Google Chrome.

17 comments

  • cat1092

    Worked like a charm for me, have been having this issue for some time.;-)

    Thanks for the Tutorial!

    Cat

  • Roopchand

    Im having this prob in my phne.. Not in the laptop… I dont see any use hardware acceleration kind of option.. What can i do..

  • phil

    My hardware acceleration was already unchecked so obviously that’s NOT a solution. disable webGL no longer exists in chrome\flags so that’s not a solution either.

  • rats webgl problem

    So after a bit of research, there are three ways you can use to fix this.

    What finally helped me was this tutorial on YouTube, that took only 2 min of my time and fixed the problem.

    https://www.youtube.com/watch?v=9L6BZNz3x9o

  • Rich

    I had to enable webgl and hardware acceleration in order to disable them. I wonder why I got an error message for something that was not enabled

    • Eilish

      I was wondering the same thing. I’ve only noticed it in the last 10 days or so, but when I followed the instructions, everything was already turned off so I don’t know if I’m missing something or what.

  • Viktor

    Thanks,
    Changing settings to not use HW accelaration worked for me.

    Did not have the option to change to not use WebGL under flags. I’m currentlyl running Chrome Version 51.0.2704.106 m (64-bit) on an old laptop with Windows 7.

  • Thomas Holzhausen

    Thanks! So webgl is basically a troll… I was scared when i saw it, and thought that my pc would explode XD

  • praveen

    Thanks sir , it works

  • Damien

    Thank you sir!

  • Kelly

    Didn’t work. Nothing works!

  • Tim

    Hi

    I did the opposite and it worked.

    For some reason today this bug was attacking very intensively and forced me to look for solution and I came across your advice.

    So, in my case, “Use hardware acceleration when available” option was unchecked in settings. And in …flags the option “Disable WebGL” does not even exist.

    I checked (enabled) the “Use hardware acceleration when available” and it helped.

    Maybe it would be helpful for someone else who has the same situation like I.

  • MARK

    yay! simple, helpful.

Leave a Reply to Thomas Holzhausen Cancel reply

Your email address will not be published. Required fields are marked *