Such problem often occures because of incorrect signature of message handle functions, that included into MFC message map for your CWnd based class.
We should very carefully check signatures such functions in comparision with expected one by MFC library. For example, if you put follow handler into message map

ON_MESSAGE(WM_SOME_USER_MESSAGE, OnMyMessage)

and define OnMyMessage as:

void CMyWnd::OnMyMessage()
{
//do something
}

this code will be compiled without errors. DEBUG build can work without any problems, but RELEASE will crash besause ON_MESSAGE macro expect follow
signature:

LRESULT CMyWnd::OnMyMessage(WPARAM /*wParam*/, LPARAM /*lParam*/)

DEBUG build works because stack processing has differences for debug and release builds.

so, the solution is simple:

Solution 1:  modify the  message handle functions with the following style and it will be ok.

void CMyWnd::OnMyMessage(WPARAM wParam, LPARAM lParam)

Solution 2:  don’t modify the message handle functios, and change the ON_MESSAGE macro to ON_MESSAGE_VOID.

ON_MESSAGE_VOID(WM_SOME_USER_MESSAGE, OnMyMessage)


This macro is in AfxPriv.h, but is largely undocumented.

• Write and read binary data in VARIANT (0)
• What is the usage of WM_NULL? (0)
• ucoGrid, a great grid control of MFC (18)
• sscanf with CString (3)
• Simple code to create an EMF or Bitmap file from existed draw code (0)
• Simple CEdit Validation (0)
• Moving selection of CListCtrl (0)
• Microsoft Visual C++ Tips (0)
• Intermittent work in UI thread (0)
• Intermittent work in UI thread (0)