Hi , is there someone that can help me to understand the leak-report in the attached image.
In this application I'm using dbgo components contained in the BDS 2006 (delphi) by Borland.
Thanks
thread Handle leak report
thread Handle leak report
- Attachments
-
- Schermata 2018-10-29 alle 18.08.26.png (134.2 KiB) Viewed 2915 times
Re: thread Handle leak report
It seems that CreateADOObject internally calls CoCreateInstance which results in RPCRT4.dll doing some stuff which ends up calling "CreateThread", and this thread handle seems to still be open at the time your application closes. This very much looks like either intended behaviour, or an intended "leak" (leaks are not really a big problem if they don't accumulate over time, so sometimes code intentionally leaks something).
In any case, it's RPCRT4.dll which is causing the leak, and most probably your code is not at fault, so you can safely ignore this reported leak.
In any case, it's RPCRT4.dll which is causing the leak, and most probably your code is not at fault, so you can safely ignore this reported leak.