Get the latest tech news

Debugging a memory leak in a Clojure service


Background Fraud Rules Service (FRS) is a rule engine in Goto Financial’s sanctions platform (my team). FRS lets you write dynamic rules to fight against fraud.

Approximately two months ago, we started seeing issues with the service where the pod’s current memory would keep increasing and exceed the request set up on Kubernetes. I’ll be skipping the things that were attempted as I want to focus on the problem caused by a Clojure core(std) library function. And drum roll, the memory usage dropped by a lot and we started planning to reduce the resources for the service.

Get the Android app

Or read this on Hacker News

Read more on:

Photo of memory leak

memory leak

Photo of Clojure

Clojure

Photo of Clojure service

Clojure service

Related news:

News photo

Clojure 1.12.0 is now available

News photo

Mimalloc Cigarette: Losing one week of my life catching a memory leak (Rust)

News photo

Phantom Menance: memory leak that wasn't there