CWinAppEx::ExitInstance() not called when exiting application

Question

0.00/5 (No votes)

See more:

Hi

I have a problem with my VC9 application when I exit it, and I found that the problem also occurs in the MFC sample 'VisualStudioDemo'. Problem is, so far I've only seen the problem occur on my PC; two of my colleagues don't get the problem at all.

Anyway here are the steps to reproduce in VisualStudioDemo:
1. Put a breakpoint in CVisualStudioDemoApp::ExitInstance()
2. Debug the application
3. In the application, create a new document, so there are two tabs open now
4. Exit the application. It doesn't hit the breakpoint.

It seems to be stuck in AfxInternalPumpMessage(). It does not have a problem exiting if I never create a new document in the application.

The fact that I am the only one so far who gets the problem tells me maybe something is wrong with my MFC DLLs but I would like a second opinion if possible! Even better would be confirmation that someone else gets the problem...

Thanks for any help.

Posted 28-Sep-11 5:58am

morrisecl

Add a Solution

Comments

Albert Holguin 28-Sep-11 13:44pm

Is it stuck or did the application close and just not hit your breakpoint?

morrisecl 29-Sep-11 4:02am

Hi Albert, it is stuck. The application does not close, ie it keeps debugging. Actually I found this morning that if I leave it long enough, it does hit the breakpoint and then close eventually (10-15 mins, haven't timed it yet though). Not sure if that's a useful clue or not.

barneyman 29-Sep-11 7:02am

10 mins is the default COM exe server timeout; are you exposing any objects from it?

Albert Holguin 29-Sep-11 10:53am

In the future, reply to my post if you want me to see it... that way I get an email notification... otherwise I won't know you replied.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Zasky · Answer 1 · 2011-09-28T21:42:00

Solution 1

I haven't used the demo app, but could it be that it has popped up a dialog asking if you want to save the document? May be the dialog is off screen or hidden in some way?

Posted 28-Sep-11 21:42pm

Zasky

Comments

morrisecl 29-Sep-11 4:00am

I don't think that is the case. The documents all seem to destruct OK, I think if it was asking to save one or both of them it would do that before destroying them.
Thanks very much for the tip though.

morrisecl · Answer 2 · 2011-09-29T03:40:00

OK I got it.

I put PreTranslateMessage in the application class, and found it was getting hammered with WM_TIMER messages from the application toolbar (an CMFCToolbar).

I had a quick look in afxtoolbar.cpp and indeed there are timers set and killed in OnMouseMove (probably something about highlighting the button while the pointer is over it).

The timer ID is defined in afxtoolbar.cpp as AFX_ACCELERATOR_NOTIFY_EVENT = 20, which is the same as what I was getting in PreTranslateMessage as the lParam.

I didn't really want to muck about with the toolbar class but a quick Google of AFX_ACCELERATOR_NOTIFY_EVENT pointed me to this article:

http://connect.microsoft.com/VisualStudio/feedback/details/529735/mfc-feature-pack-cmfcmenubar-issue[^]

In there is a workaround which seems to work for me. I won't paste it here in case something changes at their end, but the link should get you there if you want to read about it.

Thanks very much everyone who made suggestions.