Home | Blog | Software | Reviews and Features | Forum | Help | Donate | About us
topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • December 08, 2016, 02:08:13 PM
  • Proudly celebrating 10 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Nice tip on diagnosing "too little virtual memory" issues on win xp  (Read 1179 times)

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 36,416
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Just came across this nice page on diagnosing the "running out of virtual memory" issue on Windows XP, showing how to show virtual memory in the ctrl+alt+delete Windows Task Manager, which I never knew about:

http://www.askdaveta...odPagespeed=noscript

Screenshot - 12_22_2012 , 7_45_03 AM - cap 00113_thumb.png

Giampy

  • Participant
  • Joined in 2009
  • *
  • Posts: 428
    • View Profile
    • Read more about this member.
    • Donate to Member
Re: Nice tip on diagnosing "too little virtual memory" issues on win xp
« Reply #1 on: December 22, 2012, 08:24:31 AM »
Some users of XP will be surely surprised as their task manager looks differently from the one shown above (until few minutes ago I was among those users):
http://www.question-...ger-with-no-tabs.gif

A search in Internet has explained this mistery:
http://www.question-...orking-or-users-tabs
Shortly, those users must double click on the border of their task manager.
"A refrigerator without beer is like a body without soul"

f0dder

  • Charter Honorary Member
  • Joined in 2005
  • ***
  • Posts: 9,029
  • [Well, THAT escalated quickly!]
    • View Profile
    • f0dder's place
    • Read more about this member.
    • Donate to Member
Re: Nice tip on diagnosing "too little virtual memory" issues on win xp
« Reply #2 on: December 22, 2012, 11:31:53 AM »
Quote
This is one reason that Windows becomes more and more unresponsive the longer you keep it running, and why you end up eeding to restart your computer periodically.
Heh.

Yeah, gotta restart *Windows* because *applications* leak memory. What about just restarting FF and IE? :-P

Quote
Once you determine which process is using more virtual memory than it should, you need to determine what the process is. Some are pretty obvious, like winword.exe is Microsoft Word, iexplore.exe is Internet Explorer, and so on. Others aren't so obvious. The best way to determine the source of a specific process is to use a search engine to search for the Image Name as shown in Task Manager.
Which usually gives way too many junk hits these days :(. Protip: select "properties" for the process in task manager, and then "general" tab will show you the location of the process... often more useful than sifting through the junk search results.

Also: install sysinternals' Process Explorer instead of the cruddy old task manager, it's so much better :)
- carpe noctem

Tinman57

  • Charter Member
  • Joined in 2006
  • ***
  • Posts: 1,702
    • View Profile
    • Donate to Member
Re: Nice tip on diagnosing "too little virtual memory" issues on win xp
« Reply #3 on: December 22, 2012, 07:31:24 PM »

Also: install sysinternals' Process Explorer instead of the cruddy old task manager, it's so much better :)
  Yes sir, that's what I use....

f0dder

  • Charter Honorary Member
  • Joined in 2005
  • ***
  • Posts: 9,029
  • [Well, THAT escalated quickly!]
    • View Profile
    • f0dder's place
    • Read more about this member.
    • Donate to Member
Re: Nice tip on diagnosing "too little virtual memory" issues on win xp
« Reply #4 on: December 22, 2012, 07:47:15 PM »
Microsoft have improved the task manager a lot in Win8, though - on that OS, I wouldn't recommend normal people to install Process Explorer. Not that I'd recommend against it, it's just that it does so much that ProcExp isn't really necessary. Once in a while, the behemoth does something right :P
- carpe noctem