Leaking threads

[HakanL]

Hello,

I have an issue where my application seems to leak threads. I log the managed thread id on each request and as the application keeps running the ids increase (up to a point where the app stops responding). I've run .NET Memory Profiler 5 and I don't see any obvious memory leaks, but my question if there is an option in .NET Memory Profiler to trace threads and where they are created, etc?

Thanks,
/Hakan

[Andreas Suurkuusk]

If there is a thread leak, you should be able to see an increasing amount System.Threading.Thread instances when you collect snapshots. If there's a native thread look, you can enable the unmanaged resources tracker and investigate the Kernel-Thread (HANDLE) resource.

Are you seeing increasing number of threads when you collect several snapshots?

[HakanL]

Thanks for your reply. I'm not seeing any increased managed or unmanaged threads, so it must be something else then. But isn't it "odd" that the managed thread id keeps increasing? I have another project where I pump 1000s of messages through and the thread ids are always reused.

[Andreas Suurkuusk]

How are you retrieving the thread id?

There's a risk that the unmanaged resources tracker fails to identify all threads, for instance if thread handles are duplicated. Have you investigated how many threads the process has using the Task manager or Process explorer?

[HakanL]

Just using Thread.ManagedThreadId.

I checked Task Manager too and the thread count that is consistent with the thread count in the app, so I think I'm going down the wrong path. Thanks for your help!