NGEN taking up 100% of CPU after setup

David Notario (one of our developers on the CLR team) has a great explanation of this at:

On the setup side, we NGEN several assemblies in the Framework and in VS.  NGEN has three priorities and anything that isn't a Pri 1 is NGEN'd when the CPU is free (usually after setup).

I've seen several folks ask why mscorsvw.exe is taking up 100% of their CPU after setup so the link above is worth the read.


Comments (2)
  1. Mihai Limbasan says:

    Not sure to which forum post you were referring, but David’s article is at this URL:

  2. Quan says:

    Sorry, thanks to Mihai for pointing out my mistake 🙂

Comments are closed.

Skip to main content