mscorsvw

[Guest]

I've installed .net 2.0 beta 2, and now there are many instances of
mscorsvw.exe running and using all cpu. What's going on and how can I fix
this?

 

[Willy Denoyette [MVP]]

I've installed .net 2.0 beta 2, and now there are many instances of
mscorsvw.exe running and using all cpu. What's going on and how can I fix
this?

You don't have to fix what's not broken.
The mscorsvw.exe is the new .NET Runtime optimizer service (see Windows
services) that runs in the background and waits for idle time on the
machine, after installing v2.0 it will complete any outstanding compilation
jobs that have been queued.

Willy.

 

[Guest]

Thanks. The priority seemed to be too high, as it was significantly slowing
other process (both background like Oracle, and even interactive windows
explorer) running on the machine. I had to uninstall .net 2.0 to get Oracle
enough cycles to run efficiently.

 

[Guest]

Thanks for the info. Is there a way to lower the priority? Response time
for both foreground processes and other services fell through the floor. I
had to uninstall .net 2.0 to get responsiveness back.

 

[Willy Denoyette [MVP]]

Thanks for the info. Is there a way to lower the priority? Response time
for both foreground processes and other services fell through the floor.
I
had to uninstall .net 2.0 to get responsiveness back.

:

The service should only run during idle time, that means when no messages
are posted to the windows queues, and it should only run for a short period
of time needed to optimize the framework libraries.
Did you check how long it was running after v2.0 install?
Note that you can always disable the service or better pause the
optimization service by means of the "ngen queue pause" command line
command.
You can also check the status of the queue by running "ngen queue status".

Willy.

 

[Guest]

I've re-installed .net 2.0 and will monitor nscorsvw. Task manager currently
shows 63 instances of mscorsvw. This seems bit high. Is this expected?

 

[Willy Denoyette [MVP]]

I've re-installed .net 2.0 and will monitor nscorsvw. Task manager
currently
shows 63 instances of mscorsvw. This seems bit high. Is this expected?

I only noticed a few instances after installing v2.0 , I suggest you post an
issue to http://lab.msdn.microsoft.com/productfeedback/default.aspx

I would also ask you to post this to the vs2005 beta2 set-up forum at
http://forums.microsoft.com/msdn/ShowForum.aspx?ForumID=26
these forums (http://forums.microsoft.com/msdn/) are specially set-up and
monitored by MSFT employees.

Willy.