You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Globus Toolkit 6.0.1506371041 while using globus_ftp_client API and trying to contact non-existing GridFTP sever brings underlying globus_ftp_control handle into (cc_handle.cc_state == GLOBUS_FTP_CONTROL_CLOSING) state. Then globus_ftp_client level callback is called before handle moves into UNCONNECTED state. And if code using API manages to call globus_ftp_client_handle_destroy fast enough it bols down to globus_l_ftp_client_quit_callback which leads to globus_ftp_client_handle.c line 1796
/* Else --> leak! */
and globus_ftp_control handle is unrecoverably leaked without any error reported and globus_ftp_client handle destroyed.
The text was updated successfully, but these errors were encountered:
In Globus Toolkit 6.0.1506371041 while using globus_ftp_client API and trying to contact non-existing GridFTP sever brings underlying globus_ftp_control handle into (cc_handle.cc_state == GLOBUS_FTP_CONTROL_CLOSING) state. Then globus_ftp_client level callback is called before handle moves into UNCONNECTED state. And if code using API manages to call globus_ftp_client_handle_destroy fast enough it bols down to globus_l_ftp_client_quit_callback which leads to globus_ftp_client_handle.c line 1796
/* Else --> leak! */
and globus_ftp_control handle is unrecoverably leaked without any error reported and globus_ftp_client handle destroyed.
The text was updated successfully, but these errors were encountered: