Event handle leak in an idle .NET Framework 4 application


Certain Microsoft .NET Framework 4 applications leak event handles even when the application is idle.


Microsoft has confirmed that this is a bug in the .NET Framework 4. The issue occurs because the thread pool is creating and destroying threads, but it will not actually reclaim the memory and handles associated with a thread until the garbage collector runs. For some applications, this happens very rarely, because they seldom allocate managed objects.


This issue has been fixed in the Microsoft .NET Framework 4.5.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.