| 1994 1995 1996 1997 1998 1999 <2000> 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 <2000> 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | RE: memory leak - 7/10/00 cpu used is 74.7% normally 61-62% |
| From: | "Allison, Stephanie" <[email protected]> |
| To: | "Kristi Luchini (E-mail)" <[email protected]> |
| Cc: | "'[email protected]'" <[email protected]>, "Ron MacKenzie (E-mail)" <[email protected]> |
| Date: | Thu, 27 Jul 2000 17:36:00 -0700 |
Hi Kristi - >I'm having difficulty tracking down a slow memory leak in an EPICS ioc. This >ioc is a vme crate w/mv167 cpu (16MB memory) running VxWorks 5.3.1 (Tornado 1.0.1) >and EPICS R3.13.2. This memory leak occured when running EPICS R3.13.1. It appears this slow memory leak is due to message logging by CMLOG. After extremely tedious testing, it appears that ~200+/-50 bytes are lost with every message that is logged by CMLOG. I know the ioc in question logs many messages (1000's a day) compared to all other iocs here. When I use our old-style homegrown rpc message logging, no memory is lost (I suggest you try reverting back to this method and see if it makes a diff). Has anybody else seen this problem? We use cmlog R2.0.beta. Thanks, Stephanie Allison