Re: seeing memory leak in cimprovagt process

Sorry, but the way you describe your test indicates its it impossible to tell if it is Pegasus or your provider.
By running your provide in the Pegasus process, you made it impossible to distinguish the owner of the leaks.
It is only when run as a separate process that the owner of leaks can be determined.
What you should have done was to compare running Pegasus when only its internal providers were called, with when your provider is called repeatedly.
Better yet, you should have made a stub provider that did nothing but return success, and see if there are still leaks.
Another problem is that Valgrind can never determine if a service has memory leaks or not, because a service should always retain some memory.
What appears like leaks to Valgrind is exactly what all services must always do.
A service must never be out of memory, in order to be a service.
You can never determine a leak with a single event.
That is because there are normal systems events effecting memory that may simply be coincidence.

You have to make the event repeat rapidly, and then watch if there is a corresponding progression of memory loss.

 
Kirk Augustin
11821 NW McNamee Rd
Portland, OR 97231


HM: 503-289-4356


>________________________________
> From: "[email protected]" <[email protected]>
>To: [email protected] 
>Cc: [email protected] 
>Sent: Tuesday, August 7, 2012 4:14 AM
>Subject: RE: seeing memory leak in cimprovagt process
> 
>
> 
>Hi All,
> 
>Thanks for all of your response.
>We have configured cimserver “forceProviderProcesses=false”, so that all the provider processes will be in the same context.
>Now, we run “Valgrind” for cimserver process. And then, we have generated one event for our provider and stop the cimserver process after that.
> 
>Then from “Valgrind” memory leak report, we can see many definitely lost memory issue are coming from Pegasus. Please check the attached file for details of it. Is this a known issue?
> 
>Please give your valuable input. Thanks in advance.
> 
>Regards,
>Pialy
> 
> 
> 
>From:Devchandra Leishangthem [mailto:[email protected]] 
>Sent: Friday, August 03, 2012 9:52 PM
>To: Pialy Ghosh (WT01 - Manufacturing & Hi Tech)
>Cc: Anirban Bhattacharyya (WT01 - Product Engineering Services); [email protected]
>Subject: Re: seeing memory leak in cimprovagt process
> 
>Is the leak seen in a particular cimprovagt or for all the provider processes? 
>If It is seen in some particular agent processes, Then most probably it is leak in the corresponding provider. 
>See if running under a memory debugger helps for that particular agt processes. 
>
>Warm Regards 
>D>L> Meetei 
>9538270270  
>
>IBM India Software Lab, STG 
>6th Floor, A0202, 
>EGL -D,Bangalore, India 
>
>
>
>From:        <[email protected]> 
>To:        <[email protected]>, 
>Cc:        <[email protected]> 
>Date:        08/03/2012 05:37 PM 
>Subject:        seeing memory leak in cimprovagt process 
>
>________________________________
> 
>
>
>
>Hi, 
>  
>We are seeing some memory leak in cimprovagt process. We are running open Pegasus, cimserver in a windows 64 bit OS. Our provider is running on cimserver. 
>After few days long run we can see, memory usages is increased. I have searched in internet and find out same kind of problem is mentioned by others also. So, just wanted to know, is this a known issue in Pegasus? If not, then we will come to know that, issue is coming from our provider. 
>  
>Your valuable input will be very helpful for us to analyze the issue. 
>  
>Thanks & Regards, 
>Pialy 
>  
>  
>Please do not print this email unless it is absolutely necessary. 
>The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 
>WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 
>www.wipro.com 
>Please do not print this email unless it is absolutely necessary. 
>The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 
>WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 
>www.wipro.com 
>
>