{"action":"opened","issue":{"url":"https://api.github.com/repos/gperftools/gperftools/issues/976","repository_url":"https://api.github.com/repos/gperftools/gperftools","labels_url":"https://api.github.com/repos/gperftools/gperftools/issues/976/labels{/name}","comments_url":"https://api.github.com/repos/gperftools/gperftools/issues/976/comments","events_url":"https://api.github.com/repos/gperftools/gperftools/issues/976/events","html_url":"https://github.com/gperftools/gperftools/issues/976","id":310340541,"number":976,"title":"Tcmalloc heap size is much less than the real memory size from the PS command","user":{"login":"JC123456","id":17311148,"avatar_url":"https://avatars1.githubusercontent.com/u/17311148?v=4","gravatar_id":"","url":"https://api.github.com/users/JC123456","html_url":"https://github.com/JC123456","followers_url":"https://api.github.com/users/JC123456/followers","following_url":"https://api.github.com/users/JC123456/following{/other_user}","gists_url":"https://api.github.com/users/JC123456/gists{/gist_id}","starred_url":"https://api.github.com/users/JC123456/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JC123456/subscriptions","organizations_url":"https://api.github.com/users/JC123456/orgs","repos_url":"https://api.github.com/users/JC123456/repos","events_url":"https://api.github.com/users/JC123456/events{/privacy}","received_events_url":"https://api.github.com/users/JC123456/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-04-01T17:39:40Z","updated_at":"2018-04-01T17:39:40Z","closed_at":null,"author_association":"NONE","body":"Hi All,\r\n\r\nI am using the tcmalloc(gperftools-2.2) on the redhat7.2 x86_64 VM(openstack),  I face one issue during one test that the tcmalloc generic.heap_size of one process is around 19G bytes, but the physical memory size shown by the linux PS command(ps -e -orss=,args= | sort -b -k1,1n) is increasing continuously, 2G bytes are increased every hour, and now, 64G is being used.  This process has 30 work threads, one thread does the incoming message distribution to  the left threads, and it invokes MallocExtension::instance()->ReleaseFreeMemory() every 30s.\r\n\r\nDid anyone face this issue before? Is this issue related to tcmalloc itself or caused by the application program? I didn't face this issue on redhat6.2 x86_64 before.\r\n\r\nThanks,\r\nJC\r\n"}}
{"actor":{"display_login":"JC123456"}}