[omniORB] Memory leak resolution in MFC?

[Sai-Lai Lo]

To call these memory leaks is very misleading. As I have pointed out
numerous times, these heap allocated memory are for static initialised
variables or data structures which got initialised *once* on program startup.
None of these will cause your program to eat away your memory pool. 

We use purify, on Solaris and NT, to check for real memory leaks
frequently. If you can find one bug that causes the program size to
increase indefinitely I would be glad to hear that.



>>>>> Jeroen Dobbelaere writes:

> After applying those patches, the numbers of memory leaks (at exit) for
> our applications were reduced to around 30 (for both clients and
> servers), all of them still from OmniORB. (But this is better than the
> original +570 leaks for just linking with the OmniORB libraries without
> using them ;) )




-- 
Sai-Lai Lo                                   S.Lo@uk.research.att.com
AT&T Laboratories Cambridge           WWW:   http://www.uk.research.att.com 
24a Trumpington Street                Tel:   +44 1223 343000
Cambridge CB2 1QA                     Fax:   +44 1223 313542
ENGLAND