As I suggested previously, this is memory corruption. The "corrupted double-linked list" message shows up whenever glibc detects memory corruption. The fact that this always shows up with the telegram scope is a strong suggestion that the problem is caused by the telegram scope. (We regularly run scopes-api tests with valgrind, as well as various demo scopes, and they always come up clean. I'm almost certain that the problem is not in scopes-api.)
One thing that might help is to run with env var MALLOC_CHECK_=2. This forces an abort as soon as the corruption is detected, rather than waiting until something falls over the corrupted memory region.
As I suggested previously, this is memory corruption. The "corrupted double-linked list" message shows up whenever glibc detects memory corruption. The fact that this always shows up with the telegram scope is a strong suggestion that the problem is caused by the telegram scope. (We regularly run scopes-api tests with valgrind, as well as various demo scopes, and they always come up clean. I'm almost certain that the problem is not in scopes-api.)
One thing that might help is to run with env var MALLOC_CHECK_=2. This forces an abort as soon as the corruption is detected, rather than waiting until something falls over the corrupted memory region.
Closing this for scopes-api.