-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Graphd server coredump when nebula-java time-out #5750
Comments
The reason for this problem is that the
need change to
|
this is my patch
|
Amazing @flymysql would you mind PR to https://github.com/vesoft-inc/nebula-third-party/tree/master/project/patches ? @dutor could you please take a look at this? THANKS! |
Seems already addressed by https://github.com/vesoft-inc/nebula-third-party/blob/release-3.3/project/patches/fbthrift-2021-11-29.patch ? |
Oh, that's great. Since I'm still using the v3.0 version, I didn't find it fixed. |
This is a known issue, and we have fixed it with an adhoc patch. |
Please check the FAQ documentation before raising an issue
I have the same problem as in the link below, but I am not using the nebula-go client side, I am using the nebula-java client side, but the call stack of graphd crash is still the same.
Describe the bug (required)
https://discuss.nebula-graph.com.cn/t/topic/10101/13
#4635
Your Environments (required)
uname -a
g++ --version
orclang++ --version
lscpu
a3ffc7d8
)How To Reproduce(required)
Steps to reproduce the behavior:
Expected behavior
Additional context
The text was updated successfully, but these errors were encountered: