wcf - Confusing DebugDiag report to identify High Memory usage -
recently got new batch of dumps identify highmemory usage in 3 of our wcf services. hosted on 64bit apppool , windows server 2012. application 1 : processup time : 22 days gc heap usage : 2.69 gb loaded modules : 220 mb commited memory : 3.08 gb native memory : 2 gb issue identified large gc heap usage due un closed wcf client proxy objects. accounting 2.26 gb , rest cache in gc heap. application 2 : processup time : 9 hours gc heap usage : 4.43 gb cache size : 2.45 gb loaded modules : 224 mb commited memory : 5.13 gb native memory heap : 2 gb issue identified of objects of system.web.caheentry, due large cache size. 2.2 gb of string object on gc heap has roots cacheref root objects. application 3 : cache size : 950 mb gc heap : 1.2 gb native heap : 2 gb we upgrade windows server 2012, had old dumps well. dumps not show native heap same application. around 90 mb. i use windbg explore native heap !heap -s command. shows minimal native heap sizes s...