Experimental Physics and
Industrial Control System

I'm not planning to follow up on this further.

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1833108

Title:
  CA context not set during disconnect callback

Status in EPICS Base:
  New

Bug description:
  In thinking about https://github.com/pyepics/pyepics/issues/171 I did
  a quick test of adding prints to the (dis)connection and event
  callbacks in camonitor.c and find that the thread making the
  disconnect callback does not (always?) have a CA context associated
  with it.  This means that a disconnect callback which uses functions
  which implicitly pick up the CA context (like ca_pend_io() ) can
  implicitly create (and leak) a new context each time.

  In my test I find that the disconnect callback is happening on a TCP
  send thread.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1833108/+subscriptions

References:

[Bug 1833108] [NEW] CA context not set during disconnect callback mdavidsaver via Core-talk

Navigate by Date:

Prev: [Bug 1833108] [NEW] CA context not set during disconnect callback mdavidsaver via Core-talk

Next: Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0 Andrew Johnson via Core-talk

Index: 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: [Bug 1833108] [NEW] CA context not set during disconnect callback mdavidsaver via Core-talk

Next: Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0 Andrew Johnson via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024