while its in Docker, the memory leak isn't going to be docker related, its all in server.

jemalloc is in the container so testing its capabilities of leak detection is one option.

LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libjemalloc.so.2 as an environment variable to the container runtime will enable it along with the desired MALLOC_CONF.

JFYI Dmitri have yet another 4 melory leak fixed and continue. That memory leak can not be detected by usual mean because if dissconect memory will be freed.

So the question, is memory freed in this case if reconnect/dissconnect all clients?

Thank you all! I asked Customer in the case 1)if disconnecting all clients will free memory; 2)use jemalloc for leak detection. Will update JIRA again with his answers.
Adding available global and status variables to the JIRA to supplement posted before P_S reports (all for the same datetime - 8/21).

I cannot find any information in the provided stats that show any memory leaks over time.
Please ask the user to provide us with
show global status like "memory_used%";
select * from information_schema.processlist;

Run every 60 seconds to show what memory is growing.

I've attached memory used information provided by the user in CS0574876. I think this is collected in three different runs. The files are prepended with lab, test, and second_run, and were supplied by the user on different dates in that order.