In mkscott98's situation, it appears to be VisBuild.exe itself that is experiencing an error. In your case it's tclsh.exe, which isn't part of Visual Build. So they appear to be distinct problems.
Visual Build doesn't reserve memory for a process that it invokes, it simply call CreateProcess to start it. But as mentioned before, Visual Build 3.x is no longer being supported or enhanced.
|