[omniORB] IDL structure memory leak

[Jakob Happach]

Hi Fong,

the problem you describe looks similar to an effect I encountered recently.
Can you provide me a copy of the code you use to call the getFullIssue()-Method,
starting from the point, where you create your client-instance of you interface?

The problem I encountered, was located in not storing the interface-instance in
a suitable smart pointer, so it was never released, but cyclically created again and again.

Best regards,
Jakob

-------- Original-Nachricht --------
> Datum: Fri, 24 Oct 2008 13:50:54 -0400
> Von: "Qi, Fong" <FQi at tkusa.com>
> An: "Duncan Grisby" <duncan at grisby.org>
> CC: omniorb-list at omniorb-support.com
> Betreff: RE: [omniORB] IDL structure memory leak

> Hi Duncan,
> 
> The "getFullIssue()" method is I use it to get a struct data from my
> CORBA server. I saw there was 2KB increasing from that place. I wonder
> if there is a different way to pass the data I need.
> 
> Thank you,
> Fong
> 
> 
> -----Original Message-----
> From: Duncan Grisby [mailto:duncan at grisby.org] 
> Sent: Friday, October 24, 2008 1:41 PM
> To: Qi, Fong
> Cc: omniorb-list at omniorb-support.com
> Subject: Re: [omniORB] IDL structure memory leak 
> 
> On Friday 24 October, "Qi, Fong" wrote:
> 
> > I did see where the memory increased. The place was generated by
> > "omniidl" tool, which I cannot change it. I wonder if there is a way
> to
> > fix the problem from IDL file.
> 
> What exactly did it say was leaked?  That code you sent doesn't allocate
> anything at all. It's the thing that calls your application code's
> getFullIssue() method.
> 
> Duncan.
> 
> -- 
>  -- Duncan Grisby         --
>   -- duncan at grisby.org     --
>    -- http://www.grisby.org --
> 
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list