If there are any product issues, they may not be resolved using TCMalloc. Getting pstack on core file along with api/sql/filter & thread logging will help.
On Mon, Jan 14, 2013 at 8:34 AM, Simon Ellis <simon.el...@telecom.co.nz>wrote: > ** > > We implemented this back in October within our redhat environment. It > does work. However we are still experiencing memory issues when any system > process crashes and armonitor recovers. A couple of times when the recon > process crashed with a signal 11, the memory manager cannot handle it and > the physical memory justs goes up and up until eventually it gives up and > we have to restart the application.**** > > ** ** > > But with everything okay these settings do work. Reaching activities are > much better with tcmalloc installed.**** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Garrison, Sean (Norcross) > *Sent:* Friday, 21 December 2012 5:10 a.m. > *To:* arslist@ARSLIST.ORG > *Subject:* Anyone on the list ever tried the "TC Malloc" fix for ARS > (Applies to Linux ARS Servers Only)?**** > > ** ** > > ** **** > > I am just curious if anyone has tried it and had any success with it …**** > > ** ** > > > https://kb.bmc.com/infocenter/index?page=content&id=KA347994&actp=search&viewlocale=en_US&searchid=1356018348156 > **** > > ** ** > > ** ** > > Thanks,**** > > ** ** > > Sean**** > > ** ** > > ** ** > > ** ** > > _ARSlist: "Where the Answers Are" and have been for 20 years_ **** > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
