Experimental Physics and Industrial Control System
On 02/23/2017 03:29 PM, Ben Franksen wrote:
> Am 23.02.2017 um 18:26 schrieb Michael Davidsaver:
>> Personally, I'd never consider trying to unload libCom or libca.
>> Neither was designed with this in mind.
>
> Carsten (and me) wouldn't either, it's just that Labview seems to insist
> on it :-(
Is it also unloading libCom? If not then maybe you can trick it with an
new "empty" library which links against libca?
>> For example. With libCom the errlog thread is never stopped. And libca
>> registers a function pointer using epicsAtExit(). So if libca is
>> unloaded, then running epicsExit() will fail.
>
> Perhaps there should be a way to unregister the epicsAtExit callback.
At present no, though I see no barrier to your adding this.
>> There are also a number of one-time allocations which aren't cleaned up.
>
> More CA fixes needed?
and libCom. Some of these would need to be "opt in" via a cleanup function.
- 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
- Navigate by Date:
- Prev:
RE: memory leak after unloading of ca.lib Hill, Jeff
- Next:
Re: memory leak after unloading of ca.lib Ben Franksen
- 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 Carsten Winkler
- Next:
RE: memory leak after unloading of ca.lib Hill, Jeff
- 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