CA context not set during disconnect callback

Bug #1833108 reported by mdavidsaver
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

In thinking about 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.

Revision history for this message
mdavidsaver (mdavidsaver) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.