Link: https://golangweekly.com/link/59972/b208593eda
A team from Penn State University and Purdue published their latest study on concurrency bugs found in Golang projects, namely large projects from Github: Docker and Kubernetes, two datacenter container systems, etcd, a distributedkey-value store system, gRPC, an RPC library, and CockroachDB and BoltDB. The authors searched commit histories of each repository to understand concurrency bug fixes for categorization and study.
TL;DR:
- Go’s message-passing concurrency mechanism, something Go is proud of, isn’t as easy to use as it’s generally perceived. It creates just as many bugs, if not more, than shared-memory concurrency model.
- Shared memory synchronization is still used more in Go projects.
- Go’s built-in race and deadlock bug detection library still cannot catch all the bugs. There’s room for more improvements.