Error Maximum call stack size exceeded

[AmirL]

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

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

10.10.0

Framework Version

NextJs 13.5.8

Link to Sentry event

https://assisted.sentry.io/issues/6866842066

Reproduction Example/SDK Setup

After upgrading Sentry from version 7.77 to 10.10, I'm encountering a sporadic error. It doesn't appear immediately, but it consumes all the CPU resources after 10-15 hours of usage.

RangeError: Maximum call stack size exceeded
    at SyncPromise._executeHandlers (/app/node_modules/@sentry/core/build/cjs/utils/syncpromise.js:126:20)
    at setResult (/app/node_modules/@sentry/core/build/cjs/utils/syncpromise.js:166:12)
    at reject (/app/node_modules/@sentry/core/build/cjs/utils/syncpromise.js:174:7)
    at SyncPromise._runExecutor (/app/node_modules/@sentry/core/build/cjs/utils/syncpromise.js:180:7)
    at new SyncPromise (/app/node_modules/@sentry/core/build/cjs/utils/syncpromise.js:46:10)
    at notifyEventProcessors (/app/node_modules/@sentry/core/build/cjs/eventProcessors.js:17:10)
    at ? (/app/node_modules/@sentry/core/build/cjs/eventProcessors.js:31:14)
    at SyncPromise._runExecutor (/app/node_modules/@sentry/core/build/cjs/utils/syncpromise.js:178:7)
    at new SyncPromise (/app/node_modules/@sentry/core/build/cjs/utils/syncpromise.js:46:10)
    at notifyEventProcessors (/app/node_modules/@sentry/core/build/cjs/eventProcessors.js:17:10)

Everything happens inside the Sentry SDK source code.

Steps to Reproduce

It's challenging to reproduce because it only occurs on the production server and takes time to appear.

Expected Result

Normal behaviour

Actual Result

[linear]

JS-924 Error Maximum call stack size exceeded

[mydea]

Hey, can you share your Sentry.init() code (the server side one at least), and possibly any other places where you used the Sentry API manually?

What seems to be happening is that there is an error thrown in some event processor or similar, which leads to an infinite recursion 🤔

[AmirL]

Hy @mydea

Sure:

import * as Sentry from '@sentry/nextjs';
import { isNotFoundError, isUnauthorizedError } from '@/utils/httpErrors';

// Client-side instrumentation (runs in the browser)
export function register() {
    Sentry.init({
      dsn: process.env.NEXT_PUBLIC_SENTRY_DSN!,
      environment: process.env.NEXT_PUBLIC_SENTRY_ENVIRONMENT ?? 'production',
      // Adjust in production or use tracesSampler for greater control
      tracesSampleRate: 0.05,
      debug: false,
      replaysOnErrorSampleRate: 1,
      replaysSessionSampleRate: 0,
      integrations: [
        Sentry.browserTracingIntegration(),
        Sentry.replayIntegration({
          maskAllText: true,
          maskAllInputs: true,
        }),
      ],

      beforeSend(event, hint) {
        const originalException = hint?.originalException;
        if (isUnauthorizedError(originalException) || isNotFoundError(originalException)) {
          // We don't want to send those errors to Sentry, they are completely normal
          return null;
        }
        return event;
      },

      ignoreErrors: [
        'ResizeObserver loop completed with undelivered notifications',
        'ResizeObserver loop limit exceeded',
      ],
    });
}

The strange thing to me, that I expect to see some of my functions at the bottom of the stack, and I see just Sentry code there. Why would Sentry initiate something, if I don't call it?

[s1gr1d]

Hey, this is the client-side instrumentation (at least the comment says so). Can you share your server init as well? :)