An app for that?
-
I may have come to the wrong place, but is there such thing as a memory pagefile monitor/viewer for Windows? A quick google search a few weeks ago turned up nothing, but I haven't lost hope completely, so I decided to ask here Thing is, I'm running several programs under XP for long stretches of time, (sometimes weeks), which from time to time max out memory with their horrendous memory leaks, since 3/4 full virtual memory = molasses in january. The problem is that those leaks are a long term thing, and tend to pad the pagefile without noticeably affecting the process' listed memory usage. I hope there's some way to track not just PF size, but also what process makes up the bulk of it, to be able to kill and restart it without uprooting others, which may turn out to be innocent in that case Any advice will be appreciated. I'm a front end (Javascript, DOM, CSS) developer, so forgive me if the solution lies in traditional debugging tools and seems obvious. I never use those.
-
I may have come to the wrong place, but is there such thing as a memory pagefile monitor/viewer for Windows? A quick google search a few weeks ago turned up nothing, but I haven't lost hope completely, so I decided to ask here Thing is, I'm running several programs under XP for long stretches of time, (sometimes weeks), which from time to time max out memory with their horrendous memory leaks, since 3/4 full virtual memory = molasses in january. The problem is that those leaks are a long term thing, and tend to pad the pagefile without noticeably affecting the process' listed memory usage. I hope there's some way to track not just PF size, but also what process makes up the bulk of it, to be able to kill and restart it without uprooting others, which may turn out to be innocent in that case Any advice will be appreciated. I'm a front end (Javascript, DOM, CSS) developer, so forgive me if the solution lies in traditional debugging tools and seems obvious. I never use those.
I'm sure SysInternals got something. There is some VM Monitor app.
xacc.ide
IronScheme - 1.0 RC 1 - out now!
((λ (x) `(,x ',x)) '(λ (x) `(,x ',x))) The Scheme Programming Language – Fourth Edition -
I may have come to the wrong place, but is there such thing as a memory pagefile monitor/viewer for Windows? A quick google search a few weeks ago turned up nothing, but I haven't lost hope completely, so I decided to ask here Thing is, I'm running several programs under XP for long stretches of time, (sometimes weeks), which from time to time max out memory with their horrendous memory leaks, since 3/4 full virtual memory = molasses in january. The problem is that those leaks are a long term thing, and tend to pad the pagefile without noticeably affecting the process' listed memory usage. I hope there's some way to track not just PF size, but also what process makes up the bulk of it, to be able to kill and restart it without uprooting others, which may turn out to be innocent in that case Any advice will be appreciated. I'm a front end (Javascript, DOM, CSS) developer, so forgive me if the solution lies in traditional debugging tools and seems obvious. I never use those.
If you're familiar coding in C#, it shouldn't be too much trouble writing one using WMI.
SG Aham Brahmasmi!
-
If you're familiar coding in C#, it shouldn't be too much trouble writing one using WMI.
SG Aham Brahmasmi!
Hmm... So do you think the API has any means of tracking processes separately? I've seen code for monitoring PF size alone, but not much in terms of being able pick a process and see how much of the page file it makes up. I'm now thinking that the closest thing to that would be setting a "watcher" process at boot time, and have that check every memory operation, updating the process data. But then i'm only guessing. Windows does know how much memory a process uses, since killing the process triggers cleanup, and PF usage goes way down, in my case, sometimes one or two gb... I'm mostly wondering what Windows makes available in the API and what is internal. Gonna do some reading on that tonight.