Let's code together!

We're a growing, remote first engineering team. We are responsible for every aspect of building, running and securing our market leading, cloud native payment processing platform. In this space, you can learn more about us, our work, as well as catch up with our latest events.

How to find and fix memory leaks in Go applications

Imagine one day you prepare a proof of concept application. You quickly write some code that shows your idea, add tracing and metrics so you can see how it performs, deploy the application to test environment and boom, after running for 1 hour the application restarts with Out Of Memory error. This screams "memory leak", but you look into the code and see nothing obvious. You may start thinking that overall restart every hour isn't that bad. If you are thinking like that, I encourage you to keep reading as I'm going to guide you on how to debug and fix memory leaks in Go applications.

Keen to learn more about us?

Follow our engineering account on Twitter!