<< and just to clarify Larry, using your example you are right but my emphasis was a shared app on a windows network (this is very apparent with more then one user connected and at least one user is entering data) the memory usage will continue to rise as you work and not drop much no matter what you do. >>
The application is running on the local computer, or an individual session if on a terminal server. The fact that it has an data file open that happens to sit on a shared drive, and that other application instances on other computers or other sessions have the file open at the same time will have no effect on the program's memory profile where it's running. If a program's memory usage keeps growing over time it's because: 1. The program actually NEEDs more memory as time goes by (for instance, it's collecting log information in memory). R:Base will use a couple of hundred bytes of memory every time you issue a command from the R> prompt, for instance, up to whatever the limit for the history buffer is. This is not a leak, it's actual memory being used by the program. 2. It has a memory leak. 3. Some program component operating in the same process space has a memory leak (some ActiveX components run inside the host's process space and some run in their own process. In the first case, the host will appear to leak memory, in the second case you'll see the memory leak in the component, not the host). In this case, it sounds like the browser control is running in-process and leaking memory. -- Larry
