Jump to content
alogrep

Thread leaks report (FastMM4)

Recommended Posts

On 6/27/2024 at 5:01 PM, alogrep said:
The block is currently used for an object of class: IdThreadSafe.TIdThreadSafeInteger
The block is currently used for an object of class: IdGlobal.TIdCriticalSection

Those classes are both from Indy, but there is no mention of Indy in the code you have shown.  And while there are some intentional leaks in Indy related to those classes, they are registered with the RTL's memory manager and FastMM should be ignoring them (also, the leak report would look different if those leaks were actually being reported).  So, this implies that some other leaks exist in code that is not related to what you have shown here.

Share this post


Link to post

You are right Remy.

They come from nexusdb dcu's (nxBaseServerComp, nxServerManager).

I will ask them.

Thanks

 

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×