Docker Memory Leak Mac Or Ask

During the hours a particular thread is running, memory steadily and linearly increases until Kubernetes kills it because it reaches the 2GB limit I assigned.

Of course we were thinking of a memory leak, but we see something like this all the time in the gc log.

The above log line was the last log line before we see (in Graylog) that Spring Boot Tomcat is starting (hence it must have been restarted).

We see this happening exactly at the time when the memory graph reaches the 2GB line in Grafana.

Without Grafana it would have taken a while before we figured out it was something related to memory.

Somehow even after exiting and then starting Docker for Mac again, which means no containers are running, docker is already exceeding the memory allocation by 1GB.

I suspect this column is over-counting virtual memory the process has made space for, but not actually requested real memory.

There are multiple experimentations with some nice details in there.

Provide details and share your research But avoid Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

Docker Memory Leak Mac Or Ask

Not the answer youre looking for Browse other questions tagged docker memory-leaks docker-for-mac or ask your own question.

Docker For Mac Memory Leak