Comment 2 for bug 1592421

Not a lot to go off in that whoopsie log. After a short debugging session, I believe this is caused by the upgrade to go 1.6 and the following error:

panic: runtime error: cgo argument has Go pointer to Go pointer

Which is an error because the garbage collector won't be able to deal with that situation. A temporary fix is to set the environment variables GODEBUG=cgocheck=0, but this is just a workaround for whatever situation we've gotten ourselves in. I'll see if I can chase down where we are passing this go pointer illegally.