We have wcf service running inside an app pool which takes huge memory(almost 5-6gb). While monitoring, it was found that private bytes and working sets going upward, while available bytes showed a decreasing trend. The virtual bytes remained as a straight line at the top.
Debug Diag shows
<div class="groupTitle summaryGroupLabel Warning">
Warning</div> <div class="group mt20">| Description | Recommendation |
| \clr.dll
is responsible for 1.3 GBytes worth of outstanding allocations. The following are the top 2 memory consuming functions: clr!CExecutionEngine::ClrVirtualAlloc+4a:1.3 GBytes worth of outstanding allocations. clr!EEHeapAllocInProcessHeap+46:1.09 MBytes worth of outstanding allocations |
The app pool reaches a stage where it becomes non responsive to ping every 20 minutes and there is aonother entry in the event log which says the available memory is less than 5% and so
