Oh, sorry about the history mix-up. I thought you had tested a couple of versions of Netscape and Opera, including their Java modules, then uninstalled them. Dang, old brain cells, and damned few of those left, too!😱
Everything on the process list is familiar, except for cpuidle.exe, MBM5.EXE and winampa.exe. It's pretty obvious what cpuidle and winampa are. MBM5.EXE is unknown to me. I was thinking at first that it might be just a typo for the Machine Debug Manager executable (MDM.EXE), but it's something else?
At any rate, it's my understanding that memory leaks usually take the form of a slow, but continuous, increase in memory use on a static system (e.g. no changes being made). I don't think that shutting down processes after a session is necessarily going to return a system to its post-boot state. I would expect that some processes might not relinquish all memory that was free before they started when they're quit for a number of reasons. There are matters of dependency, where a process you start may cause another process or set of processes to start because of a dependency relationship. Those other processes might not, by design, shut down once the dependent process was quit. And I think that the caching of recent code / data in memory would get in the way, too.
I think the process for monitoring for memory leaks is to boot to a static condition (with the suspect process or driver loaded, of course) and leave the machine untouched in that state for a relatively long period of time while monitoring the Memory Usage History. If a continuous rise is seen, a memory leak has been confirmed. There's quite a bit of information about the exact methods for monitoring different entities for memory leaks. I've just briefly glanced at a little of it out of curiosity, because I haven't needed to make use of any of it. Therefore, my understanding of the appropriate procedures in W2K is incomplete, at best, and possibly even inaccurate. But I think you'll find what you need if you search the MSKB using the phrase "memory leak". You'll want to narrow it down to W2K, of course, because you'll get a ton of stuff about the various development environments and stuff like that in addition to information about the operating systems.
As I say, I've never had to perform this sort of analysis, probably due the my lack of a sense of adventure when choosing what to run on my systems. I'll be very interested to hear what you find.
Regards,
Jim