Re: Urgent! Memory/Resource Limitations when creating new frame in
Application Verifier is a VERY helpful tool (and it's free). I strongly suggest that you use it to
try to get to the bottom of this problem. Please read the linked article, and its children:
Application Verifier:
http://msdn.microsoft.com/en-us/library/ms220948.aspx
"NoobCoder" <NoobCoder@discussions.microsoft.com> wrote in message
news:5194942B-06C1-4A75-9DE1-1ABF601C2211@microsoft.com...
Here's the line of code. Note pDoc is a CDocument pointer.
//View hasn't been created yet or create multiple instances
CMDIChildWnd* pNewFrame = (CMDIChildWnd*)pTemplate->CreateNewFrame(pDoc,
NULL);
Here's the problem. I need to create multiple instances of the same type of
frame. It works for the first 9 frames then it crashes when creating the 10th
one.
I've traced the calls to the following found in winmdi.cpp:
HWND hWnd = (HWND)::SendMessage(pParentWnd->m_hWndMDIClient,
WM_MDICREATE, 0, (LPARAM)&mcs);
After it makes this call I see, "Windows has triggered a breakpoint ....
This may be due to corruption of the heap, and indicates a bug."
In a release build, it behaves a little bit differently. CreateNewFrame
returns a null pointer (after creating the 10th frame) at which time I prompt
the user to close some of the previously created windows, in order to open
(create) new ones. This also leads to a crash eventually... either right away
or after a few minutes.
At first I thought this might be a resources issue, but the virtual ram
usage looked 'OK', about 1.2G (windows XP.)
It seems odd to me that this occurs after a set number.