Article View: borland.public.cppbuilder.nativeapi
Article #13353Re: Borland Memory Manger leaking memory
From: Andrue Cope
Date: Fri, 17 Oct 2003 08:17
Date: Fri, 17 Oct 2003 08:17
15 lines
1375 bytes
1375 bytes
CC wrote: > Just curious if anyone has any good resources or insights on this > subject. We concluded that frequent allocations and deallocations containing a mix of large and small blocks caused freespace fragmentation in the heap. We solved our problems by introducing a memory recycling cache and small allocator. The nett effect of both is to reduce the number of calls to new and delete and keep the amounts allocated more or less the same size. -- Andrue Cope [Bicester, UK]
Technical Details
Message-ID:
<3f8fa587$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<3f8f0e05@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10cc67,b0c9f2abc30c34f3 X-Google-Attributes: gid10cc67,public X-Google-ArrivalTime: 2003-10-17 01:39:40 PST From: "Andrue Cope" <no.spam@spammy.com> Subject: Re: Borland Memory Manger leaking memory Newsgroups: borland.public.cppbuilder.nativeapi References: <3f8f0e05@newsgroups.borland.com> Organization: Vogon International User-Agent: XanaNews/1.15.7.4 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 NNTP-Posting-Host: 217.207.223.34 Message-ID: <3f8fa587$1@newsgroups.borland.com> Date: 17 Oct 2003 01:17:11 -0700 X-Trace: newsgroups.borland.com 1066378631 217.207.223.34 (17 Oct 2003 01:17:11 -0700) Lines: 15 Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail