Reasons for increasing no. "# Induced GC"


.NET CLR Memory\# Induced GC – This is the number of garbage collections that have occurred as a result of someone explicitly calling GC.

By default: 0 is the ideal no. for it.

Here are the possible reasons incase you see increase no. “# induced GC”.

1) Explicitly calling GC.Collect()
2) Calling GC.GetTotalMemory() with true i.e System.GC.GetTotalMemory(True)
3) Low on available memory and trimming Cache entries and internally making call for GC.Collect()


If you happen to know more reasons for it.I’d be happy to update the list.

Comments (2)

  1. garth says:

    Hi, specifically which version(s) of the framework & runtime are you talking about here please?

    I’ve read kb articles about 3) occurring in ASP.NET 2.0 and a hotfix was issued, and also in .NET 1.1 WinForms…

    I have an ASP.NET 1.1 web service which has some serious GC issues, one of the symptoms is exponentially increasing # Induced GC, but I don’t think it’s explicitly called anywhere.

    Is it possible the caching issue exists in 1.1 too, or some other part of ASP.NET runtime causing it?


  2. jaskis says:

    Hi Garth,

    This issue is specific to ASP.NET 2.0

    Do you see high memory usage for w3wp in question ?

    You can try capturing multiple hang dump with help of debug daig 1.1 tool. And also with me at

Skip to main content