Thank you very much for reporting and for providing the details and console logs! It's very helpful, especially since it's the second time someone reports that exact error and thus confirms a suspicion I have. Just to confirm: it worked fine in Firefox for you before the update?
Unfortunately, I'm only about half sure, I generally run everything on firefox by default on my laptop (desktop has a heavily modified version of ff and is always goofy so I can't compare the results) and only switch off if I can't otherwise do something. Usually it's a Unity compatibility fault, so I can't remember anything that would have gone wrong here before. That being said, I don't know for a fact that I wouldn't have not thought twice and just switched off if something didn't work the first time around.