BUG: App with CFormView Causes Stack Overflow or GP FaultID: Q134884
|
An application that uses a CFormView-derived class as its view may go into an infinite loop as a result of repeatedly creating CFormView windows. Depending on the compiler and linker settings, this problem may surface as a memory exception or a stack overflow.
When a CFormView receives the focus, it re-sets the focus to the control in
the CFormView that previously had the focus. The HWND of the control that
had focus last is saved in a CFormView protected member variable,
m_hWndFocus. CFormView::OnSetFocus() calls ::SetFocus(m_hWndFocus)if
m_hWndFocus is a valid window.
The problem occurs because one of the constructors for CFormView does not
initialize this member variable. As mentioned, the CFormView::OnSetFocus()
function sets focus to m_hWndFocus if it is a valid window. The problem
occurs when this variable's uninitialized value happens to be the same as
the HWND of the formview. ::SetFocus(m_hWndFocus) gives the focus to the
CFormView, which causes OnSetFocus() to be called for the CFormView again.
This causes the application to go into an infinite loop.
In the constructor of the CFormView-derived class that takes the ID of the template as an argument, initialize the m_hWndFocus variable to NULL. The constructor that takes an LPCSTR for an argument already does this. For example:
CMyFormView::CMyFormView(UINT nIDTemplate)
: CFormView(nIDTemplate)
{
// ADD THE FOLLOWING LINE TO THIS CONSTRUCTOR
m_hWndFocus = NULL;
}
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
Additional query words: 2.50 2.51 2.52
Keywords : kbprg kb16bitonly kbnokeyword kbMFC kbVC
Version : 1.5 1.51 1.52
Platform :
Issue type : kbbug
Last Reviewed: July 22, 1999