Crash Dump Analysis Patterns (Part 13i)
Although we briefly mentioned session pool in Insufficient Memory (kernel pool) pattern we decided to factor it into a separate (sub)pattern and provide WinDbg commands to analyze possible leaks. The following output shows the sequence of commands that gives you an idea although the example itself was taken from a healthy dump so no red coloring (from my memory leaks in session pool happened mostly in 32-bit past):
1: kd> !vm 4
Terminal Server Memory Usage By Session:
Session ID 0 @ fffff8800324d000:
Paged Pool Usage: 4128K
Commit Usage: 7488K
Session ID 1 @ fffff88002f65000:
Paged Pool Usage: 32852K
Commit Usage: 36488K
1: kd> !session
Sessions on machine: 2
Valid Sessions: 0 1
Error in reading current session
1: kd> !session -s 1
Sessions on machine: 2
Implicit process is now fffffa80`07d79730
Using session 1
1: kd> !poolused 8
Sorting by Session Tag
Pool Used:
NonPaged Paged
Tag Allocs Used Allocs Used
TOTAL 4 4208 9500 33475120
[...]
- Dmitry Vostokov @ DumpAnalysis.org + TraceAnalysis.org -