> At this point, there are two natural conclusions: either I have a severe hardware issue, or there is a wild memory corruption bug in the binary.

https://marcan.st/2017/12/debugging-an-evil-go-runtime-bug/

I won't spoil the conclusion. It's a long and winding path to get there and a good read. HN discussion:

https://news.ycombinator.com/item?id=15845118