Program chews up a lot of CPU when it closes

My program chews up a lot of the CPU for ~ min. It only does after I do my execution, if I exit as soon as I launch it closes with no troubles. When I close after doing my processing(a lot of number crunching, two int arrays of 525000) It opens a binary file get all my data in and then I output to a text file, with a lot of number crunchin in the middle. After I am done and get back to my main Dialog, I hit the wait state and no CPU usage, I can even run the number crunch as many times as I want and will do less cpu chewing than when I exit. Any comments, or anyone else had this problem.

I am leaning toward the large arrays that I have, because I tried using them in diffrent delcloration and got assertion failures, and another one kept giving me stack overflow problems.

GUI interface was done using MFC - please hold the comments back about the cursed microSLOTH.

Are the arrays size hard coded or are you allocating them memory dynamically?

There are 2 arrays are in an object that I declare dynamically,
when I removed the dynamically declaration for the object, I got stack over flow problems.

code as follows:

arrays declared as follows within class

const int MAX = 0x80000;

class fixdump
{
private:
int GPC_MEMORY[MAX];
int storeprotect[MAX];
int memcnt;
......... more stuff
public:
fixdump();
~fixdump();
void execute_fix();
};

/////////////////////////////////////////////////////////////////////
fixdump::fixdump()
{
first = true;
memcnt = 0;
footerval = 0;
}
/////////////////////////////////////////////////////////////////////
fixdump::~fixdump()
{
}

/////////////////////////////////////////////////////////////////////
void fixdump::execute_fix()
{

int temp = 0;
char *buff = new char;

for(int i = 0; i < MAX; i++)
{
GPC_MEMORY[i] = 0;
storeprotect[i] = 0;
}

TCHAR szFilters[] = _T ("All Files (*.*) |*.*|");
CString pop;
pop = "Please Select GPC MEMORY BINARY FILE";
AfxMessageBox(pop, MB_OK);
CFileDialog cdlg(TRUE, NULL, NULL, OFN_FILEMUSTEXIST, szFilters);
if(cdlg.DoModal() == IDOK)
{
CWaitCursor wait;

fin.open(cdlg.GetPathName(), ios::binary);
while(fin)
{
.....Crunch Numbers
}
fin.close();

wait.Restore();
output_dump(); // outputs array into file
}

return;
}
///////////////////////////////////////////////////////////////////////////
//chews CPU when closes
void CBintodumpDlg::OnOK()
{
fixdump *fix = new fixdump;
fix->execute_fix();//try threading
fix->~fixdump();
delete fix;
}

//Stack overflow problems, will not execute
void CBintodumpDlg::OnOK()
{
fixdump fix;
fix.execute_fix();
}

my guess is Windows is cleaning up caches and other resource allocations made during the execution of your program.

I would second that clean up explaination, but I changed the Release setting on MS VC++ from Debug to Release and My problem went away. I believe that in the Debug mode it was adding extra features so the debugger could have data for the developer to analysis and in release mode it no longer gathers that data. Thanks for all your help.