-
Notifications
You must be signed in to change notification settings - Fork 12
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 #20
Comments
Hi @iamnewspecies. This is not a known issue. Have you confirmed that this error is due to cls-bluebird? It seems more likely to me that it's not, or that you/Sequelize are using cls-bluebird incorrectly and not exiting contexts after each request. I guess that could result in every request being stacked on top of the last. Please come back to me when you've investigated further. |
I just had this same error in production on several servers.... |
bluebird/lib/shimOnCancel.js:41:40) |
My apologies. This does sound like it could be an bug in cls-bluebird. @DavidMorton Can you please share some more details?
I'll try to get to the bottom of this if I possibly can. |
We're getting this suddenly in production as well. Ex:
We're not using bluebird/cls-bluebird directly at all, but it's a dependency of Sequelize so somewhere under the hood they're using. We're trying to find a way to replicate outside of "let it run in production for about 2 hours...", once I can get more info I'll post here, it may help others. |
We are using Sequeilze which internally uses bluebird. To fix the logging so that it has session id which connects all our logs in one request we added cls-bluebird. But now we are seeing that we are getting "RangeError: Maximum call stack size exceeded" after our application runs for few hours.
What may cause this and is this a know issue?
The text was updated successfully, but these errors were encountered: