Reminds me of this post from 2017:

"Debugging an evil Go runtime bug" - https://news.ycombinator.com/item?id=15845118

https://github.com/golang/go/issues/20427

https://bugs.gentoo.org/637152

https://lkml.org/lkml/2017/11/10/188