Re: Debug vs Release mode - memory leak

From:

"Doug Harrison [MVP]" <dsh@mvps.org>

Newsgroups:

microsoft.public.vc.language

Date:

Tue, 22 Jul 2008 10:32:55 -0500

Message-ID:

<8cvb8457e118jb0t0eletls6tu2dqjdnj2@4ax.com>

On Tue, 22 Jul 2008 11:15:48 +0530, "John" <john@microsoft.discussions.com>
wrote:

   I have checked with some memory leak tools. But they could not identify
the leaks which are due to CStringArray objects.
I debugged line by line and paralelly checking in "VM Size" in task manager.
After calling .RemoveAll(), it dint decrease the memory. When adding strings
to this array, it is increasing the memory but not decreasing with
RemoveAll(). If I allocate on heap, it is deallocating the resources. But, I
cannot replace all CStringArray objects with TCHAR** object. This
application s there in production. How to achieve this?

  I tried to simulate this in sample application. It is working fine. Any
limitations are there with CStringArray?

  In this application, lot of CStringArray and CMap objects are there. Can
MFC manage if plenty of CStringArray and CMap objects in the application?

   Please guide me.

I explained this to you in my reply to your message in this group of Jul
17, with subject "Debug vs Release mode - memory leak". Did you miss it?
Was it unclear?

--
Doug Harrison
Visual C++ MVP