Always Be Closing: A Go Resource Leak
Not closing resources after use is a great way to accumulate leaking due to resources being retained in memory. Always closing is better than relying on automatically closes by timeout. This post dives deep into how the ‘Square’ team figured out resource leaks use various tools and debug techniques.
Appears in lists (1)
More like this (3)
How we tracked down (what seemed like) a memory leak in one of our Go microservices | Detectify Blog
The Epic Tale of Tracking Down a 'Memory Leak' in a Go Microservice — An interesting...
How I Investigated Memory Leaks using pprof on a Large Codebase