- This topic has 5 replies, 2 voices, and was last updated 1 year, 9 months ago by
.
Viewing 5 reply threads
Viewing 5 reply threads
- You must be logged in to reply to this topic.
Babis Michael.
Babis MichaelHello,
There a memory leak on the native server transports:
link: ibb.co/5Lvw5QM (add https:// before)
Thank you
Babis Michael.
kimbomadsenHi,
I cant from the screenshot you present see any leak.
I can see the two message queue processors are allocated (one for the inqueue and one for the outqueue).
Have you set InboundProcessor and/or OutboundProcessor anywhere in your code?
If you have, then kbmMW will not try to deallocate them upon close.
Further make sure you close transports upon closing your application.
/Kim
Babis MichaelHello,
Here’s the shutdown code:
Server.Shutdown;
Server.Active := False;
if ConnectionPool.ConnectionList.Count > 0 then
ConnectionPool.KillConnections;
Transport.PurgeAndClose([mwpacFlushInbound,mwpacFlushOutbound]);
The leak didn’t exist in 5.22 i’ll try to make a sample project
Babis Michaelbtw, the same leak happends to client transports too
Babis Michael.
Babis MichaelSent you a sample project via e-mail
Babis MichaelAny news ?
Thank you