Home Dashboard Directory Help
Search

setpanesize sample in mfc 2008 feature pack bug by old_geek


Status: 

Closed
 as Fixed Help for as Fixed


1
0
Sign in
to vote
Type: Bug
ID: 736941
Opened: 4/14/2012 2:15:03 PM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Memory leak upon termination:

Detected memory leaks!
Dumping objects ->
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\afxvisualmanagervs2005.cpp(32) : {355} client block at 0x0052D8C8, subtype c0, 584 bytes long.
a CMFCVisualManagerVS2005 object at $0052D8C8, 584 bytes long
Object dump complete.
The program '[2080] SetPaneSize.exe: Native' has exited with code 0 (0x0).
Details
Sign in to post a comment.
Posted by Microsoft on 5/7/2012 at 4:36 PM
Hello,

Thanks for the report. This has been fixed in the sample (and several other MFC samples) for the next release of the samples. To work around this issue, simply add a call to CWinAppEx::InitInstance at the beginning of the application's InitInstance method.

Pat Brenner
Visual C++ Libraries Development
Posted by Microsoft on 4/20/2012 at 12:29 AM
Thank you for submitting feedback on Visual Studio 11 and .NET Framework. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.

Posted by MS-Moderator08 [Feedback Moderator] on 4/15/2012 at 7:10 PM
Thank you for reporting this issue. In order to research the issue reported, we must first reproduce in our labs. Unfortunately, we are unable to reproduce the issue with the steps you provided.

Could you please provide us with a sample project zip for further investigating?

It would be greatly appreciated if you could provide us this information as quickly as possible.

Thank you
Posted by MS-Moderator01 on 4/15/2012 at 6:43 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)
Sign in to post a workaround.