RangeError <object>.set(usr/src/app/node_modules/@sentry/replay/esm/...

[bruno-garcia]

RangeError
Maximum call stack size exceeded

sentry.javascript.react, version: 7.66.0

[mtmacdonald]

We are also seeing this. For us, it seems to happen when Sentry replay is enabled, and an exception gets logged to Sentry, but the end-user leaves their browser window open for many hours. My guess is the replay feature runs out of memory.

We can see from the docs that replay is meant to stop after 15 minutes of inactivity or after 60 minutes of maximum replay. But I don't think that limit is actually working - we are seeing replay sessions that last 4+ hours (sometimes 100+ hours before the out-of-memory crash, but sometimes it happens in shorter replays, e.g. 50 mins).

[mydea]

We are also seeing this. For us, it seems to happen when Sentry replay is enabled, and an exception gets logged to Sentry, but the end-user leaves their browser window open for many hours. My guess is the replay feature runs out of memory.

We can see from the docs that replay is meant to stop after 15 minutes of inactivity or after 60 minutes of maximum replay. But I don't think that limit is actually working - we are seeing replay sessions that last 4+ hours (sometimes 100+ hours before the out-of-memory crash, but sometimes it happens in shorter replays, e.g. 50 mins).

Hey,

on what version of the SDK are you experiencing this? We've made a bunch of changes to the max. duration handling in recent versions, so I wonder if this is still happening or may be fixed already.

[mtmacdonald]

We are also seeing this. For us, it seems to happen when Sentry replay is enabled, and an exception gets logged to Sentry, but the end-user leaves their browser window open for many hours. My guess is the replay feature runs out of memory.
We can see from the docs that replay is meant to stop after 15 minutes of inactivity or after 60 minutes of maximum replay. But I don't think that limit is actually working - we are seeing replay sessions that last 4+ hours (sometimes 100+ hours before the out-of-memory crash, but sometimes it happens in shorter replays, e.g. 50 mins).

Hey,

on what version of the SDK are you experiencing this? We've made a bunch of changes to the max. duration handling in recent versions, so I wonder if this is still happening or may be fixed already.

We are building with "@sentry/vite-plugin": "^2.5.0", and running with "@sentry/browser": "^7.60.0",. Can try upgrading these.

[mydea]

We are building with "@sentry/vite-plugin": "^2.5.0", and running with "@sentry/browser": "^7.60.0",. Can try upgrading these.

Yeah, thank you - we shipped some substantial changes/improvements to this recently, so chances are this may already be fixed 🤞 keep us posted if upgrading works - thank you!