Alright,
I think I know what the issue might be. When I link against both TurboActivate.a and TurboFloat.a I am seeing this hanging behavior. Has anybody encountered this issue?
Thanks,Arie
Hi There,
So I'm building XCode, upgrading to TurboFloat 4.0 now and am finding that my code is crashing / hanging at TF_SetLeaseCallback. I am statically linking both TurboActivate and TurboFloat libraries (.a) into the same application. The libraries I am using are the ones compiled with libc++, and everything is building fine.
The problem is that the application code is hanging when it application calls TF_SetLeaseCallback. However, and this is strange, sometimes, when I debug, it gets past the line. However, even if it gets past that call, the code will then hang on TF_RequestLease. I'm not sure why my debugging isn't showing consistent results, but I would like to know what might cause the hanging. Any ideas why that might be the case? What else can I provide to help understand why it might be hanging.
Thanks,Arie
Alright,
I think I know what the issue might be. When I link against both TurboActivate.a and TurboFloat.a I am seeing this hanging behavior. Has anybody encountered this issue?
Thanks,Arie
We're going to look into this -- it sounds like a bug in our products when both libraries are used within the same product and when you're using the static versions of TA/TF. There's a similar bug report for Windows that we're looking into: https://wyday.com/forum/t/3646/crash-in-tf_requestlease-when-linking-statically-in-vs2015/
We'll update this when we have more information (can reproduce, etc.)
update: This was fixed a while ago. Use the latest version.