Running out of paged pool memory

Hi,

I posted here a couple months ago about a problem I was having where Windows XP would behave oddly when I would open and close many files.

Well, I am trying to tackle this problem again, and have come upon some more information.

I have written an application that will simply kick off 14 threads, that will perform file I/O to 14 separate hard drives. All that each thread does is, it opens a file handle CreateFile(), and then closes it CloseHandle(). I can provide source code if anyone would like to see it.

The problem that I am seeing is that the Paged Pool memory is used up very quickly. After about 15 minutes of running the application, file opens and closes take minutes to perform.

I have tried using poolmon, and have noticed that the MmSt tag has been the big hitter.
MmSt has done 53682 allocations, and 15205 frees, and it is taking up 156 megabytes, with 4064 byte per allocation. I understand the Cache Manager uses this for file caching…but how would my program cause this?

When I simply open up 2000 files and write to them without closing, I can run an application forever with no problems. So it’s something about opening and closing them…

Any help would be awesome.
Thanks,
Jake Chung

> I have tried using poolmon, and have noticed that the MmSt tag has been the

big hitter.
MmSt has done 53682 allocations, and 15205 frees, and it is taking up 156
megabytes, with 4064 byte per allocation. I understand the Cache Manager
uses this for file caching…but how would my program cause this?

Segment. The prototype PTE table used for memory-mapped files and cache.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

I’m not sure I quite understand your reply, Maxim.

I guess a question I should have asked before is also, “How can I get around
this problem?” or “How can I fix this problem?”

On 10/3/06, Maxim S. Shatskih wrote:
>
> > I have tried using poolmon, and have noticed that the MmSt tag has been
> the
> >big hitter.
> > MmSt has done 53682 allocations, and 15205 frees, and it is taking up
> 156
> >megabytes, with 4064 byte per allocation. I understand the Cache Manager
> >uses this for file caching…but how would my program cause this?
>
> Segment. The prototype PTE table used for memory-mapped files and cache.
>
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

Clarification: you see this on a CLEAN system with only your user mode application installed? If so, you have a bona fide bug that you can submit to Microsoft.

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

Yes, this problem occurs on an absolutely clean system.

How can I submit the bug to microsoft? I tried calling tech support, and
paid the 35 bucks and got no help from them.

On 10/3/06, xxxxx@osr.com wrote:
>
> Clarification: you see this on a CLEAN system with only your user mode
> application installed? If so, you have a bona fide bug that you can submit
> to Microsoft.
>
> Tony
>
> Tony Mason
> Consulting Partner
> OSR Open Systems Resources, Inc.
> http://www.osr.com
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>