Hi It seems Globus 5.2.4 still has a memory leak problem in gss_accept_sec_context().
==7809== 4,651,691 (261,200 direct, 4,390,491 indirect) bytes in 1,306 blocks ar e definitely lost in loss record 1,385 of 1,386 ==7809== at 0x4A05FDE: malloc (vg_replace_malloc.c:236) ==7809== by 0x3D7025D95D: CRYPTO_malloc (in /usr/lib64/libcrypto.so.1.0.0) ==7809== by 0x3D702D4E6C: ??? (in /usr/lib64/libcrypto.so.1.0.0) ==7809== by 0x3D702D7D19: ASN1_item_ex_d2i (in /usr/lib64/libcrypto.so.1.0.0) ==7809== by 0x3D702D83B3: ASN1_item_d2i (in /usr/lib64/libcrypto.so.1.0.0) ==7809== by 0x3D702CC0F5: ASN1_item_dup (in /usr/lib64/libcrypto.so.1.0.0) ==7809== by 0x552FEEF: globus_gsi_cred_get_cert (in /usr/lib64/libglobus_gsi_credential.so.1.4.6) ==7809== by 0x4ED2916: gss_accept_sec_context (in /usr/lib64/libglobus_gssapi_gsi.so.4.6.8) I guess this the same problem as the memory leak in gss_accept_delecation() reported by http://jira.globus.org/browse/GT-161 Regards, Osamu
