Our MLOps service written in Go was crashing - was there a memory leak, misconfiguration, or... unbound concurrency? This talk covers detecting, profiling, and fixing an unbound concurrency issue in a popular open source project, learning about how goroutines and memory are linked. A real life example of how the powerful concurrency primitives Go gives us can be misused, and how the great Go tooling helps us find these issues and fix them