Re: Problem with ExitInstance

From:

"Tom Serface" <tom.nospam@camaswood.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Tue, 1 Jul 2008 07:34:30 -0700

Message-ID:

<59221DDC-D1B3-405D-838D-978C95F0F05C@microsoft.com>

I agree with Joe. I've had occasions, mistakes on my part, where I forget
to wait for a thread to complete and then exit the program and leave the
thread stranded (pun intended). Often threads are set up to run
indefinitely (or until some condition occurs) so that part of the code just
keeps looping. I typically check for threads in my OnClose() function in
mainframe or ExitInstance and ensure that they either complete or are killed
off before exiting the program. And, if I can't stop them for some reason
(something critical is happening) then I just warn the user that it's not a
good time to exit the program.

Tom

"TonyG" <TonyG@junk.com> wrote in message
news:Btoak.282$cn7.238@flpi145.ffdc.sbc.com...

I have several copies of my program continuously running. Today I found one
copy running in a funny state which I can trace using my logs. In my App
class I have an entry for ExitInstance. In this function I do some stuff
and then I call the CWinApp base class version of ExitInstance. The problem
is that the program is not terminating. WHY??? It should right?

I also have the mystery of why ExitInstance is being called in the first
place. I know that no person is exiting my program. Is there some other
reason why ExitInstance could be called?

Part of my ExitInstance code places a entry in my log and in the event
viewer log. This is how I know this is even happening. My logs show that
ExitInstance was called twice about 1.2 seconds apart and neither resulted
in the program halting.

So my questions are:

1) Why isn't CWinApp::ExitInstance terminating the program. It should
right?

2) Why is ExitInstance being called in the first place?