-
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
storage crash, possible mem corruption #3192
Comments
A possible related problem: https://discuss.nebula-graph.com.cn/t/topic/6200. |
Not about toss, this can be repro in normal insert, if leader changed quickly.
we got a corrupted memory while debugging the core, look at the "start" "finish" and "end"
|
This was referenced Nov 1, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please check the FAQ documentation before raising an issue
Please check the FAQ documentation and old issues before raising an issue in case someone has asked the same question that you are asking.
Describe the bug (must be provided)
storage crash during stress test.
Your Environments (must be provided)
uname -a
g++ --version
orclang++ --version
lscpu
How To Reproduce(must be provided)
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
stderr output:
The text was updated successfully, but these errors were encountered: