I have a strange phenomenon. I'm starting a long-running process on Windows cmd shell (the behaviour is the same on XP and Win7). The process reads information from the file system (files, directory structure, etc.), and stores it in process memory, and then answers requests from other processes. When I terminate the process with Ctrl-C/Ctrl-Break, and re-start it, the file system information is immediately available to the process, and it doesn't have to re-read it from disk. It seems like the old process was only being swapped out, and is now swapped in again. - How is this possible? Is there a way to assure the old process memory is gone?
I was misinterpreting my app's behaviour, and was looking in the wrong places. Information was actually passed through (other) files between invocations.- Sorry for the noise.