-
Notifications
You must be signed in to change notification settings - Fork 399
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
RangeError: Maximum call stack size exceeded from async-listener #131
Comments
If you have the time, either a scenario or a test case than can reliably reproduce this crash would be incredibly helpful. This isn't something we've been able to reproduce with our own tests or sample applications, and a couple people have run into this issue now. Thanks for the report! |
I've updated to the newer version of the JS library and I haven't seen the problem since. I'll create a new ticket if I see it again. |
cmcadams-newrelic
pushed a commit
to cmcadams-newrelic/node-newrelic
that referenced
this issue
Jan 29, 2024
…97f10699871e017d50 [Snyk] Security upgrade graphql from 16.6.0 to 16.8.1
bizob2828
pushed a commit
to bizob2828/node-newrelic
that referenced
this issue
Apr 19, 2024
…/moment-2.29.2 Bump moment from 2.29.1 to 2.29.2
bizob2828
pushed a commit
to bizob2828/node-newrelic
that referenced
this issue
Apr 23, 2024
…/moment-2.29.2 Bump moment from 2.29.1 to 2.29.2
bizob2828
pushed a commit
to bizob2828/node-newrelic
that referenced
this issue
Jul 26, 2024
fix: update instrumentation to wrap getServerSideProps from renderToResponseWithComponents
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, this is an older project that has been running for years without any exceptions. I updated to the latest newrelic a couple days ago and just had this problem:
Node v0.8.18
The text was updated successfully, but these errors were encountered: