> The only way to regain my CPU is by resetting server or disconnecting >from the server, but this doesn't free any memory. dxexec is still >running at this point, but not using any CPU time. It seems that there >is a memory leak in the dxexec, but that's just a guess. any help would >be greatly appriciated. thanks, jason
Resetting the server merely clears cache pointers. It neither recovers memory, nor kills the dxexec. Disconnecting from the server should kill the dxexec process and free memory. If not, there's a bug. Occasionally, for example, on Unix (SGI) disconnecting while the dxexec is churning on a problem does not send the appropriate kill signal (or the signal is not received) and the dxexec has to be killed by hand. But normally, disconnecting ends that process, and you have to Connect to start up a new one. You should also be able to set the -memory flag to the number of MB you want dxexec to hog while it is running, at startup, in your batch file, or in the Connect Server options dialog. By default dxexec snarfs 7/8 of available memory or something to that effect. It's not a Windoze program, but a Unix program running under an Xserver, so it knows nothing about playing nice with other apps. Chris Pelkie Vice President/Scientific Visualization Producer Conceptual Reality Presentations, Inc. 30 West Meadow Drive Ithaca, NY 14850 [EMAIL PROTECTED]
