On Sun, Nov 18, 2018 at 08:44:14AM +0800, dong wrote: > First of all,I can see memory leak when I run ‘free -g’ command. This doesn't mean there's a leak. The kernel may postpone freeing memory until there's memory pressure. In particular cgroup objects are not released until there are objects allocated from the corresponding kmem caches. Those objects may be inodes or dentries, which are freed lazily. Looks like restarting a service causes recreation of a memory cgroup and hence piling up dead cgroups. Try to drop caches. >So I enabled kmemleak. I got the messages above. When I run ‘cat >/sys/kernel/debug/kmemleak’, nothing came up. Instead, the ‘dmesg’ >command show me the leak messages. So the messages is not the leak >reason？How can I detect the real memory leak？Thanks！
