sp2.1 memory leak on win2000 sp4?

I haven't noticed it (yet?) but check out the free "SysInfoMyWork" from the following link... It's a small footprint program that displays cpu usage and memory used (or free) from a taskbar icon. I've been using it for a couple weeks now and it's useful for zeroing in on leaks, etc. I've been using it to see if my system has enough physical memory.

- Eddy

Hmm, well, it's just a small icon but does not help with figuring what memory has been allocated and/or not released? Anyhow, I know it is SW which I open and SW that I close and/or about

20-50megs of system memory which is not returned after opening/closing SW. It's that simple.

..

Eddy Hicks wrote:

I have seen several instances in which SolidWorks is still running as a process, even after it closes "properly." If it crashes, most of the time it leaves something running, but even when I tell it to close & it does, about half of the time I find a process still going. Win XP Pro, SW2004 SP2.1.

WT

Hey Paul, I'm not disputing it either way. I'm just saying that the little tool can show memory before during and after launching Swx. Like I said, I'm using it to see how much of my physical memory is consumed but I've also used it a couple times to verify that a program was not releasing properly.

- Eddy

I tried it on XP Pro, SP1, and SW seems to return the memory after closing.

Jerry Steiger Tripod Data Systems "take the garbage out, dear"