MFC bug? in-process QAxServer leaves dangling COleFrameHook reference, causing destructor crash

MFC bug? in-process QAxServer leaves dangling COleFrameHook reference, causing destructor crash by Ross Brown

Closed

as Fixed

Type:	Bug
ID:	624043
Opened:	11/23/2010 11:24:25 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

Problem observed with Qt 4.7.0 (ActiveQt module) on Visual Studio 2010.
Qt developer denies that it is a Qt bug, suggesting that it is an *MFC* bug.
Full bug description, developer response, and demonstration project available here:
http://bugreports.qt.nokia.com/browse/QTBUG-15479
If you disagree with Qt developer's assertion, I will re-refer it back to them with any information you provide.

Details (expand)

Visual Studio 2010

Reliability

Fully documented here:
http://bugreports.qt.nokia.com/browse/QTBUG-15479

English

Windows 7

English (US)

Closing TstCon while ActiveQt-wrapped Qt control remains instantiated causes assertion failure. Apparent cause: Dangling COleFrameHook reference causes it to be destroyed after the CFrameWnd to which it refers has already been destroyed.

No assertion failure should occur.

0 attachments

Posted by Microsoft on 1/14/2011 at 1:17 PM

Hello Ross,

Thanks for the report. This was indeed a bug in MFC and it has been fixed for the next major release of Visual Studio.

Pat Brenner
Visual C++ Libraries Development

Posted by Microsoft on 11/23/2010 at 7:57 PM

Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 11/23/2010 at 12:23 PM

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)