-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Node.js crashed with the following stacktrace #29435
Comments
Even though this is a different backtrace, it may be the same underlying issue as #29353. |
@nodejs/http2 |
@jsloop42 would you mind to add a way to reproduce this crash? Could you try using Node 10 and see if the issue persists? |
Please find the code that produces the crash.
This crashes even if I fetch the collection with pagination and runs the string similarity algorithm on it. Since I am using Firebase as the deployment target, the node version I am having to use is v8 as the environment does not support other versions as of now. |
I’ve looked into this, but with the limited information available, I’d say either this is also addressed by #29399, or we need more information (e.g. a reproduction, a core dump, etc.). |
Please find the debug log.
|
@jsloop42 Thanks, but a reproduction or a core dump or something along those lines would really be more helpful. The npm debug log doesn’t really say more than that there was an error. |
Please find a crash log.
|
I'm still having a similar problem when receiving a lot of messages from @google-cloud/pubsub.
|
I have same crash when use pubsub subscription. |
Updated to 10.18.0. Everything is ok there. But Node 10 is Beta in Google Cloud Functions. |
@dobromyslov thanks for your confirmation. Node.js v8.x is end-of-life and won't receive any fixes anymore. I am closing this, since the issue seems to be specific about v8.x. If it does happen on any other release line, please leave a comment so that this is reopened. |
Node.js crashes before sending response with the below stack trace.
The server uses Firestore as the backend. Kindly let me know how to fix this.
The text was updated successfully, but these errors were encountered: