devenv.exe 和 svchost.exe 都占用整个 CPU 并且占用线程在堆栈跟踪的顶部具有相同的功能

Question

我正在使用没有扩展的 visual studio 2010 SP1Rel 并且 devenv.exe 进程连续使用整个核心，这使得 IDE 的使用非常困难，如果不是不可能的话。

我注意到 svchost.exe -k netsvcs 也在使用整个核心。

我已经运行 Process Explorer 试图确定发生了什么，我注意到这两个进程都有一个线程占用所有 CPU 并且两个线程都在同一个函数中 ntoskrnl.exe!KeSetEvent+0x6ca

svchost.exe 的堆栈跟踪是

ntoskrnl.exe!KeSetEvent+0x6ca
ntoskrnl.exe!KeWaitForMultipleObjects+0xd52
ntoskrnl.exe!KeWaitForSingleObject+0x19f
ntoskrnl.exe!PoStartNextPowerIrp+0xbb4
ntoskrnl.exe!PoStartNextPowerIrp+0x1841
ntoskrnl.exe!PoStartNextPowerIrp+0x1ab7
wuaueng.dll!DllInstall+0x6c2c
wuaueng.dll!DllInstall+0x6cd3
wuaueng.dll!DllInstall+0x6977
wuaueng.dll!DllInstall+0x116be
wuaueng.dll!DllInstall+0x12177
wuaueng.dll!DllInstall+0x2a702
wuaueng.dll!DllInstall+0x27316
wuaueng.dll!DllInstall+0x25a88
wuaueng.dll!DllInstall+0x62e5
wuaueng.dll!DllInstall+0x59db
kernel32.dll!BaseThreadInitThunk+0xd
ntdll.dll!RtlUserThreadStart+0x21

devenv.exe 的堆栈跟踪是

ntoskrnl.exe!KeSetEvent+0x6ca
ntoskrnl.exe!KeWaitForMultipleObjects+0xd52
ntoskrnl.exe!KeWaitForSingleObject+0x19f
ntoskrnl.exe!PoStartNextPowerIrp+0xbb4
ntoskrnl.exe!PoStartNextPowerIrp+0x1841
ntoskrnl.exe!PoStartNextPowerIrp+0x1ab7
cslangsvc.dll+0x5a08
cslangsvc.dll+0x5a7b
cslangsvc.dll+0x1f8cd
cslangsvc.dll+0x1fbae
cslangsvc.dll!_FileCodeModel_GetTopLevelParseEvents@24+0x328dc
cslangsvc.dll!_FileCodeModel_GetTopLevelParseEvents@24+0x32c5f
cslangsvc.dll!_FileCodeModel_GetTopLevelParseEvents@24+0x32655
cslangsvc.dll!_FileCodeModel_GetTopLevelParseEvents@24+0x327ff
cslangsvc.dll+0x308af
cslangsvc.dll+0x3079e
cslangsvc.dll+0x308af
cslangsvc.dll+0x3079e
cslangsvc.dll+0x308af
cslangsvc.dll!_BaseNodeOwner_Release@4+0x29901
cslangsvc.dll!_BaseNodeOwner_Release@4+0x298ba
cslangsvc.dll+0x3079e
cslangsvc.dll+0x308af
cslangsvc.dll+0x3079e
cslangsvc.dll+0x308af
cslangsvc.dll+0x23600
cslangsvc.dll+0x235b1
cslangsvc.dll+0x23600
cslangsvc.dll+0x235b1
cslangsvc.dll+0x23600
cslangsvc.dll+0x235b1
cslangsvc.dll!_FileCodeModel_GetTopLevelParseEvents@24+0x6279
cslangsvc.dll!_FileCodeModel_GetTopLevelParseEvents@24+0x2c8b4
cslangsvc.dll!_FileCodeModel_GetTopLevelParseEvents@24+0x2bb91
cslangsvc.dll!_FileCodeModel_GetTopLevelParseEvents@24+0x2bbb4
cslangsvc.dll!_FileCodeModel_GetTopLevelParseEvents@24+0x2b509
cslangsvc.dll!_LangService_IsRunningUnitTests@4+0xc3b
cslangsvc.dll!_FileCodeModel_GetTopLevelParseEvents@24+0x2b019
cslangsvc.dll!_FileCodeModel_GetTopLevelParseEvents@24+0x2acbb
cslangsvc.dll+0x255bb
cslangsvc.dll+0x2558c
Microsoft.VisualStudio.TextManager.Interop.ni.dll+0x4d5ea
Microsoft.VisualStudio.Editor.Implementation.ni.dll+0xa17cc
Microsoft.VisualStudio.Editor.Implementation.ni.dll+0xa16a1
clr.dll!DllCanUnloadNowInternal+0xaa94
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x14fbc3
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x14f740
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x14c867
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x1566a1
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x1562fa
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x155cf6
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x1557af
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x153ed4
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x153e35
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x15a3a0
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x153662
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x153075
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x15286f
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x15204e
Microsoft.VisualStudio.Platform.VSEditor.ni.dll+0x16848e
WindowsBase.ni.dll+0xbb432
WindowsBase.ni.dll+0xbb36a
WindowsBase.ni.dll+0xbda3c
WindowsBase.ni.dll+0xbd988
WindowsBase.ni.dll+0xbd8ab
WindowsBase.ni.dll+0xba23b
WindowsBase.ni.dll+0xba3da
WindowsBase.ni.dll+0xbb61b
WindowsBase.ni.dll+0xbb56b
WindowsBase.ni.dll+0xbb432
WindowsBase.ni.dll+0xbb36a
WindowsBase.ni.dll+0xb9b0e
WindowsBase.ni.dll+0xbaef1
clr.dll+0x2936
msenv.dll!DllGetClassObject+0x379b1
msenv.dll!DllGetClassObject+0x37521
msenv.dll!DllGetClassObject+0x375aa
msenv.dll!DllCanUnloadNow+0x190f
msenv.dll!DllCanUnloadNow+0x1840
msenv.dll!DllCanUnloadNow+0x17a1
msenv.dll!DllCanUnloadNow+0x176e
msenv.dll!DllCanUnloadNow+0x16b0
msenv.dll!VStudioMain+0x78
devenv.exe+0x10637
devenv.exe+0x10fd4
devenv.exe+0x120d8
devenv.exe+0x12148
ntdll.dll!RtlInitializeExceptionChain+0x63
ntdll.dll!RtlInitializeExceptionChain+0x36

有人以前看过这个吗？我希望有人能指出我正确的方向，因为我不知道如何进行。我已经多次重新启动 visual studio 并重新启动多次但无济于事。启动 VS 几分钟后，devenv.exe 问题再次出现，svchost.exe -k netsvcs 问题来来去去。

任何帮助，将不胜感激。谢谢

Answer 1

我不确定为什么，但关闭我在 visual studio 中打开的大部分文件似乎可以解决问题

devenv.exe 和 svchost.exe 都占用整个 CPU 并且占用线程在堆栈跟踪的顶部具有相同的功能

devenv.exe and svchost.exe both hog an entire CPU and the hogging thread has the same function at the top of the stack trace

cpu-usage

visual-studio-2010

visual-studio

devenv