-
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 #146
Comments
Same here, but a different trace:
node-newrelic 1.7, node 0.10.28 |
@johanneswuerbach are you getting the timeout in similar situation? Just trying to figure out if its the same case or slightly different. |
I see this crash happening after some minutes, but no specific load. Downgrading to 1.5.3 fixed it for me. |
Upon brief inspection, it looks like That's an easy enough fix, probably in the next release. |
The flatten.js issue should be fixed now in the release last week, version 1.7.2. Please give it a spin and see if it resolves the issue. It may only resolve the problem @johanneswuerbach saw, rather than the issue @nukulb saw. |
Since there hasn't been any movement on this ticket in a while, I'm going to close it out. We're also moving support to our dedicated support portal at http://support.newrelic.com. If you continue to have any issues, please follow up there. We appreciate your understanding as we undergo this transition. |
/home/admin/dist/node_modules/newrelic/lib/timer.js:106
if (this.durationInMillis >= 0) return this.durationInMillis;
^
RangeError: Maximum call stack size exceeded
There is specific request where the server is grinding through some stuff for 2mins or so and then right after that request is returned to the client, the server dies with the RangeError above.
Turning newRelic off fixes the issue.
The text was updated successfully, but these errors were encountered: