-
Notifications
You must be signed in to change notification settings - Fork 40
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
cockroachdb hit SIGSEGV in Go runtime during test run #1144
Comments
I was running this:
like this:
It ultimately failed like this:
That panic is pretty early in the test setup process. We were waiting for CockroachDB to start, but it exited instead. The entire test log file consists of:
Here are all the files in the CockroachDB directory, sorted in ascending order of modification time (most recently modified last):
Let's take a look at the CockroachDB stderr:
I believe this is the key piece of output from that:
It seems that we hit a SIGSEGV inside the Go garbage collector? Unfortunately, it looks like it exits the process rather than allowing I've created a tarball with what seems like all the information I have, including the CockroachDB directory and the log file:
I've attached it to this issue (it's a tarball inside a ZIP file because GitHub doesn't support attaching tarballs directly): I would not expect this to be very reproducible, but just to check, I reran the CockroachDB command line reported in the log, which would use the exact same parameters and storage directory. It did not crash:
I'm probably not going to dig deeper into this any time soon. |
This seems quite possibly a result of the same issue that caused #1146 but I don't see how we'll ever know that unless we hit the same issue again with core dumps enabled. |
Closing this since we haven't seen it since that issue was resolved. We can reopen if we start seeing it again. |
While trying to reproduce #1130, I ran into a new problem where CockroachDB appears to have hit a SIGSEGV in golang.
The text was updated successfully, but these errors were encountered: