-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Closed
Closed
Copy link
Labels
A-build-systemB-os-macosIssues specific to macOS.Issues specific to macOS.C-investigationFurther steps needed to qualify. C-label will change.Further steps needed to qualify. C-label will change.S-2-temp-unavailabilityTemp crashes or other availability problems. Can be worked around or resolved by restarting.Temp crashes or other availability problems. Can be worked around or resolved by restarting.
Description
When running cockroach start --store=type=mem,size=30% ...
, pressing Ctrl+C/sending SIGINT
results in a crash during shutdown. The log below contains both stdout and stderr output.
Please describe the issue you observed, and any steps we can take to reproduce it:
To Reproduce
^C
*@spacecraft~⦕ tail cockroach.log
r11 0x213
r12 0x0
r13 0x3
r14 0x33
r15 0x0
rip 0x405ed1f
rflags 0x213
cs 0x2b
fs 0x0
gs 0x0
*@spacecraft~⦕
What did you do? Describe in your own words.
I started cockroach
2.0.5 using in-memory storage, and it crashes on SIGINT
.
Expected behavior
Not crashing--graceful shutdown.
Additional data / screenshots
cockroach.log
Note that it crashes regardless of any SQL being run.
Environment:
*@spacecraft~/go/src/my_project⦕ cockroach version
Build Tag: v2.0.5
Build Time: 2018/08/13 20:55:02
Distribution: CCL
Platform: darwin amd64 (x86_64-apple-darwin17.7.0)
Go Version: go1.10.3
C Compiler: 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.2)
Build SHA-1: 3f2f0f5eea9b9d552e471eba8c37504a0595342f
Build Type: development
*@spacecraft~⦕ uname -v
Darwin Kernel Version 18.0.0: Wed Aug 22 20:13:40 PDT 2018; root:xnu-4903.201.2~1/RELEASE_X86_64
Installed from brew install cockroach
on macOS Mojave.
Additional context
Metadata
Metadata
Assignees
Labels
A-build-systemB-os-macosIssues specific to macOS.Issues specific to macOS.C-investigationFurther steps needed to qualify. C-label will change.Further steps needed to qualify. C-label will change.S-2-temp-unavailabilityTemp crashes or other availability problems. Can be worked around or resolved by restarting.Temp crashes or other availability problems. Can be worked around or resolved by restarting.