5gb memory and 1.5gb swap file and froze Windows. WindowBlinds' injected DLL suddenly started eating up huge amounts of memory until it filled my. I used to have a similar nasty problem involving Google Desktop and WindowBlinds. If you are seeing something more significant, it's possible what you are seeing is caused by a third-party application injecting a DLL into Process Explorer. Unless you keep Process Explorer running all the time the memory it leaks is negligible. NET, which aims to eliminate leaks and buffer overflows, among other things). Fortunately some more modern ones keep track of memory for you (of note is. programming languages traditionally have not made it easy to keep track of allocated memory. I am sure many commercial applications leak more. KuHGL: If you are talking about an increase of 4kb every 5 seconds. also the treeview's intrinsic meaning has been what I was looking for on many occasions. Mostoften searching for a handle that locks a drive or directory or spying on the commandline switches of launched processes. and some versions are quite instable.īut i appreciate the features, when i need them. I don't use it for taskkilling in emergency situations. i was able to kill tasks blindly when windows was unable to redraw the screen. though it has more features (info collumns), than many of these. it is faster than more simple and better known taskkillers, because of it's programming language. It will remember it's own priority so set it to "real time" (right in the tasklist as you would with every other process). it kills stuff that windows task manager can't kill. It gets the most important tasks done: showing CPU, killing and setting priority with keyboard. However it is incredibly fast at starting, even when another program is eating all the cpu.
it's not popular on google and developement is done. I use an old program called "nt process viewer" on windows XP.
0 kommentar(er)
