Experimental Physics and
Industrial Control System

On 02/23/2017 05:26 PM, Hill, Jeff wrote:
> 
>>> The CA client library _is_ cleaning up all of its allocations if
>> ca_context_destroy is explicitly called, but this is of course not universal for
>> components in libCom and or EPICS base.
>>
>> https://github.com/epics-base/epics-base/blob/3.14/src/ca/access.cpp#L139
>>
>> https://github.com/epics-base/epics-
>> base/blob/3.14/src/ca/ca_client_context.cpp#L56
> 
> It does appear, from my perspective, to be cleaning up there but I could have another look if that’s not the case.

It is cleaning up with epicsExit(), not ca_context_destroy().

Replies:

Re: memory leak after unloading of ca.lib Carsten Winkler

References:

memory leak after unloading of ca.lib Carsten Winkler

Re: memory leak after unloading of ca.lib Michael Davidsaver

Re: memory leak after unloading of ca.lib Ben Franksen

RE: memory leak after unloading of ca.lib Hill, Jeff

Re: memory leak after unloading of ca.lib Michael Davidsaver

RE: memory leak after unloading of ca.lib Hill, Jeff

Navigate by Date:

Prev: RE: memory leak after unloading of ca.lib Hill, Jeff

Next: Question about PV operation that defined in ai.template. lzf neu

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 

Navigate by Thread:

Prev: RE: memory leak after unloading of ca.lib Hill, Jeff

Next: Re: memory leak after unloading of ca.lib Carsten Winkler

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