Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure to contact GridFTP server always leads to globus_ftp_control handle leak. #10

Open
akonstantinov opened this issue Nov 13, 2017 · 0 comments

Comments

@akonstantinov
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant