Sentry-javascript: RangeError: Maximum call stack size exceeded

Created on 4 Mar 2020  路  6Comments  路  Source: getsentry/sentry-javascript

Package + Version

  • [x] @sentry/browser
  • [ ] @sentry/node
  • [ ] raven-js
  • [ ] raven-node _(raven for node)_
  • [ ] other:

Version:

5.12.4

Description

Sentry sends RangeError: Maximum call stack size exceeded error from @sentry/utils/instruments.ts.

Here is Sentry event: https://sentry.io/share/issue/82cc1c5e3bc4418ebccecee6c324d9d1/

Browser: Chrome Mobile WebView 64.0.3282
Platform: Android 7.1.1

Needs Information Needs Reproduction

Most helpful comment

It looks like your code might have an infinite event loop. And because we collect breadcrumbs through wrapping native API, it looks like it comes from Sentry.
You should be able to see where it originates from by blackboxing either our bundle or CDN file (or instrument.ts itself if you have access to sourcemaps) in devtools. Devtools => Settings => Blackboxing.
Line 85 in helpers.ts points to user-land function invocation, which would confirm my suspicions.

All 6 comments

It looks like your code might have an infinite event loop. And because we collect breadcrumbs through wrapping native API, it looks like it comes from Sentry.
You should be able to see where it originates from by blackboxing either our bundle or CDN file (or instrument.ts itself if you have access to sourcemaps) in devtools. Devtools => Settings => Blackboxing.
Line 85 in helpers.ts points to user-land function invocation, which would confirm my suspicions.

@kamilogorek Thanks for the detailed explanation.

Anytime. Please feel free to ping me if it's still relevant issue, I'll reopen it.

Please explain more considered we are very new in angular.

I'm not sure what I could explain more other than what my comment above did 馃槄

I am getting a similar error

RangeError null.<anonymous>(@sentry.hub.src:scope.ts)
error
Maximum call stack size exceeded

I am using nextjs so I have sentry logging errors from the backend and the frontend. This error originates in the backend.
I am using it this way:

server.use(Sentry.Handlers.requestHandler());

// my routes ...:

server.use(Sentry.Handlers.errorHandler());

Any idea?

Was this page helpful?
0 / 5 - 0 ratings