[jreposa]

I tried Airbrake yesterday and it wasn't that helpful. I had to turn it off quickly as I was inundated with errors.

You can see from your screenshot that you're getting Script Error at line 0. A number of other errors pop up that I couldn't quite figure out.

For instance, when the variable 'google' isn't found it's because the google javascript never loaded. But, how many browsers are rejecting the google maps javascript?

[dmethvin]

It sounds like Airbrake was very helpful. It is telling you that users are experiencing errors frequently, something you didn't know before. If, for example, the "google javascript never loaded" situation is common you'd want to either fix that or have your own script work around it -- at the very least, let the user know why the page is broken and that it isn't your fault.

Line 0 script errors can be from dynamically loaded code, such as JSONP requests or `eval()` code.

[jreposa]

Well... Yes. It was helpful for that reason. I waded through many of the errors and traced them back to actual lines of code. It just so happens that many of the errors weren't particularly useful to me. I.e., not actionable.

Our browser tests include IE7, IE8, IE9, Safari, Firefox and Chrome. None of those errors are present in our tests. As you note, in many of the cases I could wrap the errors with notifications to the user.

But, really, if the google variable isn't loaded for a small set of users and I can't easily configure a test system that can reproduce it, I'm not going to take the time right now. I have too many other pressing things on my list.

[martian]

The "google" variable is often not loaded for people who use Adblock or similar extensions that block social media plugins. You can simply check that "google" exists before running the code that depends on it:

    if (typeof google !== "undefined") {
        // run google code here
        google.magic();
    }

[dmethvin]

I understand deadlines, and yes you may not be able to do more than explain to the user that there is a problem out of your control. But don't diss Airbrake because you don't have time to investigate and/or fix. They're not sayin' you have to fix it, they're just sayin'.

[jreposa]

Just to clarify... I love Airbrake. Apologies if it didn't come across as that way. I use it on every site and app we create.

[ecaroth]

FF/Chorme/Safari also give the Line 0 "script errors" when an error occurs in any JS file that isn't on your domain (IE jquery from a CDN, 3-rd party scripts, etc). This is a cross-origin security feature.

[rakeshpai]

The developer of Errorception (http://errorception.com/) here.

"Script Error" at line 0 only occurs in Firefox - I know, I'm in the business of collecting errors ;). It seems to happen when the JS file couldn't be parsed correctly. The cause for this usually partially downloaded files on the client trying to be passed through the interpreter.

Other than some little HTTP tweaks that can be done, there's very little else that you can do with "Script Error"s. So, we don't even bother sending "Script Error at line 0" errors to the server. For all practical purposes, it's a meaningless error.

[fudged]

Have you sent this issue to the Firefox team? :)

[rakeshpai]

I would, but I'm not sure if Firefox is "wrong". That may be a subjective opinion, though.

[webbruce]

That's what it's suppose to do lol. I use Airbrake and knowing exactly when I get an error (via email) is super important for customer satisfaction.

[jreposa]

Agreed. I attack the most pressing errors ASAP. It just that the errors weren't actionable. Check out my reply above.