leaks reported by fpcx64mm while using indy for TMS MQTT about indy HOT 3 CLOSED

The TIdThreadSafeInteger and TIdCriticalSection leaks are expected and intentional. See the comments regarding FREE_ON_FINAL in the initialization/finalization sections of the IdThread.pas and IdStack.pas units.

FREE_ON_FINAL is not defined by default, and so these expected leaks are registered with the memory manager so they are not included in leak reports - at least, on systems that support this feature, which unfortunately does not include FPC at this time (see the REGISTER_EXPECTED_MEMORY_LEAK and HAS_System_RegisterExpectedMemoryLeak defines in IdCompilerDefines.inc).

Ignoring expected leaks works only on Delphi versions that have System.RegisterExpectedMemoryLeak(), or which have re-compiled Indy to use FastMM, MadExcept, or LeakCheck libraries directly.

If you want to avoid the leaks, and take the risk that they are trying to avoid, then you can recompile Indy with FREE_ON_FINAL defined in IdCompilerDefines.inc.

The rest of the leaks reported are not related to Indy.

from indy.

Just to mention that idSSLOpenSSL.pas , IdComponent, IdTCPClient, IdTCPConnection, IdGlobal, IdContext, IdIOHandlerSocket, IdIPAddress are used by TMS MQTT

from indy.

Thanks a lot Remy.
I read the comments in the code.
the 217 error was due to my code with threads and it is fixed now. But it help to learn better indy.

from indy.