EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Memory Problem related to CA?
From: "Jeff Hill" <[email protected]>
To: "'Paul Sichta'" <[email protected]>, "'Schoeneburg, Bernd'" <[email protected]>
Cc: [email protected]
Date: Fri, 14 Mar 2008 14:38:24 -0600
> I also have a memory leak in my 3.14.7, vxworks (T2.2.1), which
> occurs when I do large (~16 kB) CA transfers.   Haven't looked
> too hard, yet.

The R3.14 IOC software was checked with purify (on windows) for memory leaks
at various times during its initial release, and it was given a clean bill
of health (by purify).

What you might be seeing is CA's retaining various blocks on its free lists
for future reuse.

Jeff

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Paul Sichta
> Sent: Friday, March 14, 2008 10:47 AM
> To: Schoeneburg, Bernd
> Cc: [email protected]
> Subject: Re: Memory Problem related to CA?
> 
> I also have a memory leak in my 3.14.7, vxworks (T2.2.1), which
> occurs when I do large (~16 kB) CA transfers.   Haven't looked
> too hard, yet.
> 
> -ps
> 
> 
> Schoeneburg, Bernd wrote:
> > Hi all,
> > on some IOCs we see that the free memory becomes less and less.
> > Especially when we restart our channel archiver, the free memory in the
> > IOCs becomes much less.
> > My possible explanation for this is that channel access has not a free
> > memory block of the desired (big) size in its private pool, so that
> > additional memory from the system pool is allocated - and never free'd.
> > Is this possible? Can the channel access pool become fragmented? If YES:
> > Is there a solution for this in later versions? Or a patch?
> >
> > We are using Epics 3.13.10 with vxWorks 5.3.1 on mvme162-532A (16 MB)
> >
> > Thank you
> >
> > Bernd
> >


References:
Memory Problem related to CA? Schoeneburg, Bernd
Re: Memory Problem related to CA? Paul Sichta

Navigate by Date:
Prev: RE: Memory Problem related to CA? Jeff Hill
Next: EDM fundamentals .... Emmanuel Mayssat
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Memory Problem related to CA? Paul Sichta
Next: RE: Memory Problem related to CA? Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·