| 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 | 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: [Merge] ~info-martin-konrad/epics-base:dont-nuke-global-cac-thread-id-in-exit-handler into epics-base:3.15 |
| From: | mdavidsaver via Core-talk <[email protected]> |
| To: | [email protected] |
| Date: | Mon, 06 May 2019 18:18:03 -0000 |
Yes, ref. counting would probably be the best way to avoid an exit handler here. I think this could be done with an atomic inc. in ca_context_create() and dec. in ca_context_destroy(). And then I notice that caClientContextIdOnce in access.cpp is already being leaked... So maybe just remove "cacExitHandler()"? This would be far from the only one-time leak in Base. -- https://code.launchpad.net/~info-martin-konrad/epics-base/+git/epics-base/+merge/366996 Your team EPICS Core Developers is subscribed to branch epics-base:3.15.