I installed .net 2.0 beta 2. After 2 days, mscorsvw continues to dominate the CPU. Other process such as logon and Oracle DB take about 3 times longer to execute.
I experienced the same issue on my Win2k Server OS running SP4 and every patch Windows Update can find. During installation I assume the last step is to NGEN since now that I have installed twice both time the "mscorsvw" process continually throws exceptions until I reboot. Once reboot the "optimization" service takes over the computer until I get so frustrated that I Uninstall the Framework.
Prior to running the install on the Win2k computer though I ran the VS 2k5 install, which installs the 2.0 Framework, on my Window XP Pro computer it completed without error or problem. This is why I am lead to believe that it is an OS difference problem. Just though I would post my finding so everyone can benifit a little.
I noticed that the Feedback post said that the issue has been fixed. So is there a release date for a build that contains the fix
Installed C# express two hours ago and the mscorsvw process is still running. This process is pre-compiling classes How long is it supposed to take The task manager will not let me set the priority of the task which is currently set to normal and it is slowing everything down. I have no cpu idle time at all.
Installed C# express two hours ago and the mscorsvw process is still
running. This process is pre-compiling classes How long is it
supposed to take The task manager will not let me set the priority of the
task which is currently set to normal and it is slowing everything down.
I have no cpu idle time at all.
It precompiles the high priority assemblies first,
that should take 5-10 minutes only, it is not supposed to slow everything down
as it should run as a low priority process unless you do a lot of IO or your
system is low on memory. Once the low priority assemblies are done it compiles
the low priority ones during system idle time.
I am having the same problem as everyone else. I am running a 1.6 Ghz Centrino CPU and have 512 MB of Ram. I left my computer on and alone for the most of yesterday and all of last night to get rid of this process, but when I woke up this morning it was still going.
How long is it supposed to take on a machine like mine I'd like to see how far it is, how long it will take, and be able to specify that I want it to run at once - could that be added to the next Framework beta installer
mscorsvw will not stop running
Sacblonde
http://blogs.msdn.com/davidnotario/archive/2005/04/27/412838.aspx
Chris Bernholt
I experienced the same issue on my Win2k Server OS running SP4 and every patch Windows Update can find. During installation I assume the last step is to NGEN since now that I have installed twice both time the "mscorsvw" process continually throws exceptions until I reboot. Once reboot the "optimization" service takes over the computer until I get so frustrated that I Uninstall the Framework.
Prior to running the install on the Win2k computer though I ran the VS 2k5 install, which installs the 2.0 Framework, on my Window XP Pro computer it completed without error or problem. This is why I am lead to believe that it is an OS difference problem. Just though I would post my finding so everyone can benifit a little.
I noticed that the Feedback post said that the issue has been fixed. So is there a release date for a build that contains the fix
sharif_m
Laurent CP
Installed C# express two hours ago and the mscorsvw process is still running.
This process is pre-compiling classes How long is it supposed to take
The task manager will not let me set the priority of the task which is currently set to normal and it is slowing everything down. I have no cpu idle time at all.
cpk
go to the vs command console and type:
ngen queue pause
Jeff
cominfo
Frogers
J. Hedrick
How long is it supposed to take on a machine like mine
I'd like to see how far it is, how long it will take, and be able to specify that I want it to run at once - could that be added to the next Framework beta installer
Again, is it normal to still be running