A real-world walkthrough of diagnosing and fixing a Go memory leak that caused OOM crashes in a Kafka consumer service. Covers Go memory fundamentals (stack vs. heap, GC tricolor algorithm, TCMalloc-based arenas), then details two concrete fixes: using Uber's automaxprocs to correctly set GOMAXPROCS in Kubernetes containers,

8m read timeFrom medium.com
Post cover image
Table of contents
Part 2: Tools and Strategies for DebuggingGet Kader Genç’s stories in your inbox
2 Comments

Sort: