[omniORB] Client side leak in release build using CORBA::any

[David Hyde]

This message was written a while a go and I have resolved the issue, though
not completely to my satisfaction.

Yes,  everything is linked to the correct libraries - I've been over these
with a fine tooth comb.  What eventually fixed the problem was to remove the
reference to msvcstub.lib (and msvcstubd.lib in the debug build) and the
problem went away!  Note that the leak was only seen in applications that
dealth with CORBA::any.

Thanks

David


-----Original Message-----
From: Duncan Grisby [mailto:dgrisby@uk.research.att.com]
Sent: 15 April 2002 12:27
To: David Hyde
Cc: OmniOrb mailing list (E-mail)
Subject: Re: [omniORB] Client side leak in release build using
CORBA::any 


On Monday 25 March, David Hyde wrote:

> I'm using omniORB 3.0.2 on Windows 2000 with VC++ 6.0.

> Even with the client doing nothing the release build leaks memory
> like a sieve every time the data is pushed to it.  We're talking 20
> - 40k every few seconds with messages being constantly produced.
> The debug build is fine.

In the release build, have you built absolutely everything as release?
If not, the debug and release bits of code use different memory pools.
Usually that causes crtIsValidHeapPointer exceptions, but sometimes it
can just leak memory.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan@grisby.org     --
   -- http://www.grisby.org --