Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

After clean install and boot of OS Windows x64 I launched cmd.exe (any other exe) and closed it. Then I launch rammap.exe (http://technet.microsoft.com/en-us/sysinternals/ff700229.aspx). On the 2nd page called "Processes" I sorted list by process name and saw that cmd.exe still consumes memory (4K Private and 16K Page table = 20K). I launched it 2nd time and new item appears in this list (one for every process launch+termination). So every process termination takes 20K of memory away.

If you have software frequently launching and terminating processes on such server OS you will spot that after some days or weeks OS begins to show strange errors (usually about not enough memory). And more days after that everything you have to do is to restart OS. After restarting it works fine for nearly the same period of time.

I registered this problem on every 2008 server R2 x64 (+SP1 and -SP1) and indirectly (rammap doesn't support) on 2003 Server x64.

The problem is not observed on Windows 7 x32 (+SP1 and -SP1).

Screenshot enter image description here

See the first step in exploration of this problem Page table fast growth

Can anybody disprove or approve my assumption and observation? Can anybody tell how to work around this behavior? Is it bug or is it not?

share|improve this question
    
Presumably you've created a case with MS for this right? –  Chopper3 Apr 2 '11 at 20:08
    
Chopper3, My knowledge of English is not perfect. Please clarify phrase "a case with MS". –  tormozit Apr 3 '11 at 6:20
    
I mean have you called Microsoft. –  Chopper3 Apr 3 '11 at 10:44
    
Not yet. I have not done it before. –  tormozit Apr 3 '11 at 10:56
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.