the application on zones. Jordan Vaughan wrote:
As Steve said, libumem will be your best tool for this job.Is the program zone-aware? The program might behave differently (i.e., its logic is different) while running in non-global zones and the alternative code paths might be leaking memory.Jordan On 12/17/09 11:23 AM, Steve Lawrence wrote:I recommend using libumem on the application. Some folks were nice enough to write about it.http://blogs.sun.com/pnayak/entry/finding_memory_leaks_within_solarishttp://blogs.sun.com/dlutz/entry/memory_leak_detection_with_libumem -Steve On Thu, Dec 17, 2009 at 12:09:11PM +0200, AdinaKalin wrote:Hello, I'm struggling with the following problem and I have no idea how to solve it. I'm testing an application which is running fine on a global zone,but memory leaking when installed on a local zone.The local zone has its whole root and a very simple, basic configuration:bash-3.00# zonecfg -z mdmMDMzone zonecfg:mdmMDMzone> info zonename: mdmMDMzone zonepath: /mdmMDMzone brand: native autoboot: true bootargs: pool:limitpriv: default,dtrace_proc,dtrace_user,proc_priocntl,proc_lock_memoryscheduling-class: FSS ip-type: shared net: address: 192.168.109.14 physical: e1000g0 defrouter not specified One of the application processes, when started on global zone, has anrss of about 5 GB ( prstat -s rss ) and it keeps this size to the end ofthe test. If I stop the application on global zone and I start it onlocal zone, the same process starts with the normal size ( 5gb on prstat-s rss ) but is growing during the test ( I saw it 25GB on a server with 32 gb RAM ) until is failing. I don't understand why is thisbehavior and if the application has a memory leak, why I don't see it onthe global zone. Any help is more than welcome!!!_______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org_______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org
<<attachment: Adina_Kalin-Florescu.vcf>>
_______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org