IndexSizeError getting logged in raven code

[natenorberg]

Do you want to request a feature or report a bug?

bug?

What is the current behavior?

This error keeps getting logged occasionally.
IndexSizeError
~/raven-js/src/raven.js in o.prototype.captureMessage at line 382:0

It doesn't seem to be causing any real problems to the end users and the whole stack trace is within raven.js. I'm not sure if this is really a problem, but I figured I'd write it up here instead of just ignoring it.

[MaxBittker]

Hi Nate - could you post the entire stack trace? Because I associate this error with canvas/dom apis, I have the feeling that this is not a raven.js issue (but could be wrong). Does your page use the canvas?

[natenorberg]

Yeah, here you go:

at o.prototype.captureMessage(~/raven-js/src/raven.js:382:0)
at o.prototype.captureException(~/raven-js/src/raven.js:329:0)
at r(~/raven-js/src/raven.js:282:0)

I'm not positive it's a raven issue either. We do have a couple canvases in the app, but it looks like they shouldn't have been rendered when the error was thrown.

[MaxBittker]

not quite enough for me to reproduce this, and still inclined to think that this is an error originating in the other code that raven is hiding or displaying in a confusing way. could you try disabling raven?

one easy way to do this if you use CDN raven and run an adblocker is to add it to your adblocker rules, or otherwise just commenting it out of your build. Thanks nate!

[natenorberg]

I'll keep an eye on it I guess. I haven't ever seen it locally, so I wouldn't really be able to tell if disabling raven changes anything :/

Thanks for taking a look

[benvinegar]

This is not a bug in Raven.js – this is just the point at which Raven captured the error by wrapping a function call in try/catch.

I added a comment in #847 to try and address this.