You thought you didn't have tio think about memory management and memory leaks when you were done with C? Think again!

Join me starting the dive by looking at how golang allocates and deallocates memory, and the workings of the garbage collector. Learn how the stack and heap works. And why does my substring allocate so much memory?

We'll dive into some pitfalls we all are guilty of, and some that are real edge cases. We're looking at code, and coding patterns. What can cause your application, website or k8s operator to consume increasingly amounts of memory? And how to avoid it without crashing out in a OOM (Out of memory) error?

And can I actually answer all of my own questions? Maybe more? Will you even know without joining in?