In the process of updating mochi-tests to ssg 0.5 API (changes are not committed yet) and I'm hitting a deadlock here on the client side:
#0 ssg_release_mid_state (mid_state=0x60b00001e650) at ../src/ssg.c:2434
#1 0x00007ffff757b04c in ssg_group_descriptor_free (descriptor=0x60d0000951c0)
at ../src/ssg.c:3045
#2 0x00007ffff7541880 in ssg_finalize () at ../src/ssg.c:183
#3 0x0000555555559e89 in main (argc=9, argv=0x7fffffffd2d8)
at ../perf-regression/margo-p2p-latency.c:204
It looks like ssg_release_mid_state() might be attempting to acquire a lock ssg_rt that is already held by the parent ssg_finalize() function.
In the process of updating mochi-tests to ssg 0.5 API (changes are not committed yet) and I'm hitting a deadlock here on the client side:
It looks like ssg_release_mid_state() might be attempting to acquire a lock ssg_rt that is already held by the parent ssg_finalize() function.