Re: Memory leak with CAsyncSocket::Create
"Doug Harrison [MVP]" <dsh@mvps.org> wrote in message
news:kad893pun39rv6hlti7dt50kgu2j43kue2@4ax.com...
On Tue, 10 Jul 2007 13:45:46 -0700, "Michael K. O'Neill"
<MikeAThon2000@nospam.hotmail.com> wrote:
"r norman" <r_s_norman@_comcast.net> wrote in message
news:2895939efidggi556s7fbje0euhm2jd2d0@4ax.com...
I have traced a memory leak problem to CAsyncSocket::Create(). Is
this a known problem? Is there a workaround/solution/fix? Here is
sample code:
for (int i=0; i<m_nReopenCount; ++i) {
CAsyncSocket *pAS = new CAsyncSocket;
pAS->Create();
pAS->Close();
delete pAS;
}
Running this 1000 times uses up 1200 KBytes of memory, or just over 1
KByte per call. Commenting out the Create() leaves memory clean. (And
please don't complain about my bracketing style -- I like it.)
This is a known problem, acknowledged by Microsoft.
Apparently, when using CAsyncSocket in a GUI app that also has XP visual
styles (themes), there is a memory leak. The problem seems to be
OS-dependent, and it might exist only under XP (running themes). It did
not
manifest itself under Win 2000, and it might be gone now from Vista.
For one report, see "CSocket Consuming Memory Uncontrollably" at
http://www.codeguru.com/forum/showthread.php?t=353944 . I am fairly
certain
that this is the same problem that you are seeing, since this report also
includes the exact same number for the amount of leaked memory (i.e.,
1200
bytes per call to Create()).
There is a parallel posting in the newsgroups at "HELP!! CSocket and
CAsyncSocket Consumes Memory Uncontrollably" in the
microsoft.public.win32.programmer.networks newsgroup, at
http://groups.google.com/group/microsoft.public.win32.programmer.networks/b
rowse_frm/thread/8490cdb5c4f18c76/b87332dbee0cb54c?tvc=1
The "solution", if you can call it that, is to disable themes. See
"CAsynCSocket Memory Leak Fix" at
http://www.codeguru.com/forum/showthread.php?t=370761
Interesting! The problem appears to be the creation of a top-level,
non-child window by CAsyncSocket::AttachHandle. For example, if I replace
norman's loop body with the following, I observe the same "leak" in
Process
Explorer:
CWnd* p = new CSocketWnd;
#if 1
p->CreateEx(0, AfxRegisterWndClass(0), 0,
WS_OVERLAPPED, CRect(), 0, 0);
#else
p->Create(AfxRegisterWndClass(0), 0,
WS_CHILD, CRect(), AfxGetMainWnd(), 0);
#endif
p->DestroyWindow();
delete p;
If I use #if 0, a child window is created instead, and I don't observe the
leak.
--
Doug Harrison
Visual C++ MVP
That *is* very interesting. When we looked at this two years ago, we
noticed that the leak disappeared when creating a child window, but we
didn't look any furhter, and we didn't think to try a top-level window. We
eventually concluded that the problem was related to the creation of the
socket's hidden window, but that it didn't show itself unless XP visual
styles (themes) was enabled, i.e., inclusion of a manifest with the program.
With a top-level window, does it make a difference as to whether themes is
or is not enabled? Was our answer back then completely off-base?
Mike