RangeError: Maximum call stack size exceeded

[MathiasWP]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases #12859

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/sveltekit

SDK Version

8.12.0

Framework Version

8.12.0

Link to Sentry event

https://sentry.io/organizations/kvist/issues/1940072/events/64b75fa4/?project=4507447454990416

SDK Setup/Reproduction Example

Sentry.init({
	dsn: PUBLIC_SENTRY_DSN,
	tracesSampleRate: 1.0,
	normalizeDepth: 10,
	integrations: [
		Sentry.browserProfilingIntegration(),
		Sentry.browserTracingIntegration(),
		Sentry.replayIntegration({
			maskAllText: true,
			blockAllMedia: true,
			maskAllInputs: true
		}),
		Sentry.captureConsoleIntegration()
	],
	replaysSessionSampleRate: 0.01,
	replaysOnErrorSampleRate: 1.0,
	profilesSampleRate: 0.1,
	maxValueLength: 8192,
	environment: import.meta.env.MODE,
	enabled: !dev,
	beforeBreadcrumb: this.breadcrumbFilter
});

Steps to Reproduce

I don't know what the user did, there was no suspicious behaviour in the issue.

Expected Result

No maximum call stack size should be exceeded.

Actual Result

[lforst]

Hi, seems like you deleted the issue in Sentry. If you toggled the "full stack trace" switch, how many frames were shown and what were they?

[MathiasWP]

Hi, seems like you deleted the issue in Sentry. If you toggled the "full stack trace" switch, how many frames were shown and what were they?

I haven't deleted the issue. Does this URL work? I tried following the placeholder url in the issue template: https://kvist.sentry.io/issues/1940072/?environment=production&project=4507447454990416

[MathiasWP]

This is the full stack trace:

[lforst]

Seems weird. I'd imagine the stack trace to be way larger for a "maximum call stack size exceeded" error. There are also no recurring frames which would indicate that we have some bad patching loop. Is this a one-of error or does this happen consistently? Do you have any sort of custom instrumentation logic?