sentry-javascript: Errors in rrweb

Sentry Issue: JAVASCRIPT-2B7E

TypeError: Cannot read properties of undefined (reading 'prototype')
  at Array.forEach (<anonymous>)
  at new Promise (<anonymous>)
...
(18 additional frame(s) were not displayed)

One source of missing replay accounts appear to be here, where our SDK is erroring, but we tag events with the replayId anyways.

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 18 (8 by maintainers)

Most upvoted comments

@mryraghi you are right that this is not a good user experience and I will make sure that this is given the right attention. In particular you are completely correct that the answer cannot be that you need to do your own house keeping here. Sentry has a feature called “spike protection” which is supposed to prevent this from happening. We will make sure to look at this, and the recommendations given out by support as well.

However independent of how we are dealing with spikes we need to resolve the issue that our own integration can be the source of errors and we will have a look at resolving this as well.

mitsuhiko on Feb 2, 2023

Hi there,

we just released 7.37.0, where we completely re-vamped the rrweb error suppression. Now, hopefully no rrweb errors should ever bubble up to Sentry anymore.

If you still see any replay/rrweb specific errors in Sentry after upgrading to 7.37.0, please let us know, but hopefully this issue is now solved for good.

mydea on Feb 10, 2023

@mryraghi : Thanks for surfacing this. This is definitely not a great experience and as @mitsuhiko mentioned, our spike protection feature should have caught this anomaly. We’re working on enhancements to this feature and will be rolling this out over the coming weeks. We’ll be posting more details here too. (I just reached out to you separately as well)

gauthamcs on Feb 2, 2023