Disheartening, but not unfamiliar - very reminiscent of Java days. I would
highly encourage removing any dependencies that use CGO or Unsafe - and move to
pure Go. This seemed to be the only way to tame these sort of errors in the
wild in Java land.
Also, have you done stress tests using the r
Hi all,
We develop an open source program for consumers that has a reasonably large
usage within its niche, on a mix of operating systems and platforms. Recently
we enabled crash reporting to get panic traces back from cooperating users.
With that we've discovered a bunch of panics of our own c
