my .Net application is leaking handles into lsass.exe

Hi all,

i'm trying to find the root cause of this weird behavior

I wrote an application 3 years ago in .net 4.5 (and updated to 4.5.2) that was running fine on win 7 32bit on Mini-PC barebone

in last 3 months I've revamped hw with 64bit win 10 and I just installed same executable which is compiled .Net and JIT 

every week (or after  4 5 days) the mini-pc is unresponsive and I found that lsass.exe is starving, moreover after activating "Russinovich mode" I discovered that lsass.exe was accumulating > 50k handles, while may application is constantly under 1000 handles.

but If I kill my application lsass.exe handles count return under 3k

I ask if everybody knows correlation among security token / login validation that could generate invalid / orphan handles on lsass.exe ?
Is there any tool in vstudio for tracking .net call vs lsass.exe ?

thanks in advance
Diego

Diego scaravaggi (Freelancer)