Just to sort of close out this thread, the official response from Qlik is to look at these two sources, neither of which describes my problem and told that the case would be referred to R&D but there is no remedy to the problem. I guess no one else has this problem or don't use Qlik as we do.
I agree that this is one of the MOST FRUSTRATING aspects of Qlik. I have made it a habit of making sure to load new changes to the data model interactively or using debug and to always leave the script dialog open to make sure I can kill the application before saying ok. And we have implemented constraints on most tables to prevent viewing them before making multiple filter selections.
But, these work-arounds do NOT resolve the underlying problem.
I'm not aware of any other development software that I use that has this problem.
I do not have access to either of the two Case articles listed in the end of the thread, but I hope that Qlik will acknowledge and fix this problem.
The cases described how Qlik allocates memory during a reload and the information was not pertinent to this problem. Regardless of how it uses memory or machine resources, in no way should a product utilize 100% of the machines resources giving the user no chance to even kill the process.