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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: memory leak after unloading of ca.lib |
From: | Michael Davidsaver <[email protected]> |
To: | "Hill, Jeff" <[email protected]>, Ben Franksen <[email protected]>, "[email protected]" <[email protected]> |
Date: | Thu, 23 Feb 2017 16:08:13 -0500 |
On 02/23/2017 03:50 PM, Hill, Jeff wrote: > >>> There are also a number of one-time allocations which aren't cleaned up. >> >> More CA fixes needed? > > 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