-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
RangeError: Maximum call stack size exceeded in @sentry/remix server instrumentation #16075
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for writing in! Are there any more stack frames shown in the error message? I'd like to understand where we are potentially calling things too deeply. |
Unfortunately nothing else. |
That is odd. Can you check that you don't have any |
Sentry.init() is definitely called once. We don't use addEventProcessor |
Hello we are facing the same crash with SDK v9.13 and remix v2.16.5
To make the init in |
We'll take a look! |
Resolves: #16075 We used to allow rewrapping of the root loader when we had a separate Express adapter, where we could not determine the instrumentation order. Now that we don't have it anymore, we can remove this. Still, can't reproduce the original issue running e2e test apps under load. But it's clear that's what caused it.
A PR closing this issue has just been released 🚀This issue was referenced by PR #16136, which was included in the 9.15.0 release. |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/remix
SDK Version
9.12.0
Framework Version
Remix 2.16.5
Link to Sentry event
No response
Reproduction Example/SDK Setup
Environment
Node.js: v20.19.0
Sentry Remix SDK version: 9.12.0
Using ZenStack enhanced Prisma client
Using pnpm package manager
Steps to Reproduce
Expected Result
No crash.
Actual Result
Crash.
The text was updated successfully, but these errors were encountered: