Babis Michael

Nope, changing keepalive values didn’t help!

Changing SetKeepAlive to 20 instead of 5 seems to resolve the problem … Keep testing …

function TkbmMWAbstractSocket.SetKeepAlive(ASocket:THandle):Integer;
begin
//Result:=TkbmMWSocketAPI.SetKeepAlive(ASocket,5,3,5);
Result:=TkbmMWSocketAPI.SetKeepAlive(ASocket,20,3,5);
end;

btw, It would be nice to have it on a property or something to be…[Read more]

Hmm, seems TkbmMWCustomTCPMessagingClientTransport.InternalCloseSocket; called twice but TkbmMWAbstractSocket.Destroy; called once!

Hmm, still getting leak on the native client transport when i shutdown the app with 5.20.01

nice 🙂

I guess this will fix the Socket memory leak too right ?

Thank you

Thank you i’ll give it a try 🙂

the native messaging! with the indy messaging i do this with the code on the first post!

Thank you

Yes, i’m using the messaging transport.
IOW, i want to kill all active connections/requests instantly and not wait to timeout.

Thank you

Rtx 3090 and 4k monitor! You’ll notice that the server application will be busy (can’t do anything) when you switch to DirectX mode.

This is NOT fixed in 5.20! You forgot one NativeUInt!
Pbyte(NativeUInt(@InData1)+i-1)^:= Pbyte(NativeUInt(@InData1)+i-1)^ xor Pbyte(longword(@InData2)+i-1)^;
^^^^^^^=NativeUInt

Thank you

Changing to capture mode DirectX freezes server!

Kim, this isn’t fixed in 5.20! (you forgot it)

Love you!

Kim ?

The client connects but it doesn’t display anything!

btw, added manually and works!