Crash in TF_RequestLease when linking statically in VS2015Solved

The current version of TurboFloat 4.0.9.3 crashes in TF_RequestLease when linking statically x64 (VS2015) and also linking TurboActivate 4.0.9.3 statically x64 (VS2015)

If only one library is linked statically the function works as expected. But as soon as TurboFloat as well as TurboActivate are linked statically the function first throws an boost::interprocess::interprocess_exception followed by an access violation.

I'v tested this with a small console application that calls: TF_PDetsFromPath -> TF_GetHandle -> TF_SetLeaseCallback -> TF_RequestLease (<<<< crash - access violation)

Please let me know when a fix is available. Thank you.

Hi, are there any news on this?Thanks and best regards

We still need to work to reproduce this on our side.

I think I'm seeing the same issue in XCode here. If I statically link both of them I'm getting hangs / crashes on code that calls the TurboActivate or TurboFloat functions. Is it possible to not statically link both of them in an application? I kinda need to do this.

Thanks,Arie

You can use both in an app, we're still looking into this.

Are there any news regarding this issue?

We have not been able to reproduce this. Can you provide an example app that reproduces the crash you're describing?

I think this is the same issue crashing my application. Similar configuration in VS2013, linking both static libraries. The application can function when using the TF dll but usually hangs on the final call to TF_Cleanup.

A trace of my debug build shows TF_RequestLease dying with a bad value passed into a crypto library routine. If IPC messages are getting mangled (from buffer overflow, for example), this might be the source of the bad data.

We've made new builds for TA and TF that should fix both of these issue. If you're still getting problems let us know.

Also, the versions of TurboActivate and TurboFloat must match if you want to use both static libraries in your app. If you want to use mis-matched versions then you'll need to use at least 1 dynamic library version of either (or both) TA/TF.

Get the latest versions here: https://wyday.com/limelm/api/

Reply
Discard post