Windows XP virtual memory.

[Baldy18]

Windows XP was constantly running out of virtual memory when I had it manually set to a maximum of 756MB so I set it to system managed size. Now it often alerts me that it is increasing the size and often has a size of about 1.5GB, how rediculous! My question is how do I figure out what program or programs are using so much virtual memory? I have a feeling that the ebay enhanced picture editor and IE may have something to do with it and I'm also getting runtime errors when using those.

Systems specs.

Windows XP
IE7
Athlon XP 2200+
512MB RAM

 

[lxskllr]

ebay enhanced picture editor

I don't know what that is, but if you're editing large pictures a tremendous amount of ram can be used.

I have my initial size set to 1.5gb, and let Windows manage the rest.

 

[IEC]

I would just let Windows manage the pagefile, but that's just me...

 

[corkyg]

Originally posted by: Baldy18
512MB RAM

Therein lies part of your problem. For dealing with digital imagery, etc., you need much more RAM. With only 512 MB, you should let Windows totally manage your page file size.

I work with digital imagery frequently - each picture can be 5 MB or more. And, you also need some "freeboard" during your operations. If I only had 512 MB of RAM, I would have Windows start virtual memory at 2 GB.

 

[degibson]

You can simply use the task manager to find out which processes are using your memory.

 

[Smilin]

Task manager might be the easiest way. Just configure it to display some more columns.

You can also use perfmon and fire up the memory counters and the process memory counters.

OLD article on perfmon:
150934 How to Create a Performance Monitor Log for NT Troubleshooting
http://support.microsoft.com/d...x?scid=kb;EN-US;150934


Dumpheap can be an easy way as well. You just take some before and after snapshots..This is probably the most serious way to troubleshoot this without getting extreme and having to use poolmon, umdh..
253706 How To Isolate and Identify the Source of Inetinfo or Other Process Memory Leaks
http://support.microsoft.com/d...x?scid=kb;EN-US;253706


If it's kernel memory (pool) rather than heap you should get some 202x events in your system log. You can also use poolmon:
177415 How to use Memory Pool Monitor (Poolmon.exe) to troubleshoot kernel mode memory leaks
http://support.microsoft.com/d...x?scid=kb;EN-US;177415

For the less faint of heart..
268343 Umdhtools.exe: How to use Umdh.exe to find memory leaks
http://support.microsoft.com/d...x?scid=kb;EN-US;268343

 

[JACKDRUID]

start->run-> perfmon

 

[Baldy18]

Thanks everyone.