1 reply
by csmith
If you can just restart the program to solve the problem this is not the traditional memory leak. With a traditional memory leak the PC has to be restarted to free the memory, because the OS (Windows) has not freed the memory after it is no longer used.
This could be a memory leak within the program, where it does not free the child memory when the child process stops.
This problem can also come from cacheing problems. (Saving too much "undo" information)
On troubleshooting this problem:
Have you watched the Hard Drive LED on the PC case to see if Windows is starting to use excessive Virtual Memory?
As you know, when Windows exhausts installed RAM it starts writing to the hard drive (virtual memory)
(I am assuming that virtual memory is enabled.)
The other obvious first step is to run a utility to check memory use.
This does not sound like a conventional memory problem (640K) , this does sound like an extended memory problem.
It is a good idea to also check resource usage, but resource exhaustion isn't very likely in this situation.
Well, This is a start.
Regards, Chris
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending