>You said in another thread that you've done C++ development. If so, you should know the answer is nope, you can't do that. When you get memory leaks, memory gets in a corrupt state. There is no way to say what issues it caused. What if it writes into the memory used by another application? How does it reset that?


My use of the term "memory leak" refers only to malloc()'d, not free()'d, memory allocation. Objects that were created, never destroyed, just hanging around until the process terminates.