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
Kernel crash on macOS #23680
Comments
How repeatable is this crash? Does your machine crash when running other
processes? Have you tired removing Little Snitch?
…On 3 February 2018 at 18:58, Emmanuel T Odeke ***@***.***> wrote:
/cc @randall77 <https://github.com/randall77> @ianlancetaylor
<https://github.com/ianlancetaylor> @dvyukov <https://github.com/dvyukov>
@rsc <https://github.com/rsc>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#23680 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAcA20Y0LMy4HmJMhOD7QzJFBlRt8vIks5tRBGxgaJpZM4R4FSz>
.
|
I was able to reproduce it one more time on the same machine. Still running it on the other MacBook I have with different hardware, but with very similar software, down to Little Snitch. And yes, I will try to remove it later and check again – I suspect it too. |
Also remove virtualbox and parallels and all non-Apple stuff to figure out if you actually found a macOS kernel bug. |
There’s a kernel debug kit that may help get some of the symbols: https://developer.apple.com/hardwaredrivers/ Why don’t Go symbols make it to this trace? |
I wasn't able to reproduce that issue anymore, even on the same configuration, running it for days. 😐 Closing. |
What did you do?
I was running maintnerd (
maintnerd -config=go -debug
starting with empty$HOME/var
) built with race detector, and it killed my OS.I'm pretty sure nothing can be done about it now (there are too little details), but I created an issue to see if someone else is experiencing this problem, and also to have a Google hit for it.
I will try to reproduce it on all my hardware.
Crash report
System details
The text was updated successfully, but these errors were encountered: