Replies: 1 comment 4 replies
-
Converted to a discussion because more likely than not this is a bug in the add-on and not in node. Node blocks SIGPIPE by default so if the process gets killed by that signal, then it probably means something unblocked it. And indeed, this line in the stack trace looks rather suspicious:
|
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Version
14.15.3
Platform
Linux NRP10 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
uv
What steps will reproduce the bug?
There are no exact steps to reproduce the issue but it occurs almost every night. also this issue does not occur on every deployment, it occurs only at a single deployment bu causing production downtime.
How often does it reproduce? Is there a required condition?
The issue occurs almost every night when the production rate is very high.
What is the expected behavior?
node should show where exactly it is crashing on which input. Also if there are additional steps/tools that I can use to pinpoint the root cause, please let me know.
What do you see instead?
Additional information
Below is the coredump for the same crash:-
Beta Was this translation helpful? Give feedback.
All reactions