Terrible brakes at compile time in Visual Studio?

Question

C++ / C#

Good afternoon!
Recently (perhaps after some updates) Visual Studio has become very heavy on the computer during compilation. Very strong - this is "stuttering" of music on Core i7, given that cl.exe (C ++ compiler) is executed with a "low" priority (the base priority of the application can be configured in the registry), this is simply nonsense. After some time trying to understand what is happening with the computer, I noticed that during compilation, the kernel time (“Kernel Time”) in the task manager reaches 90+% of the total CPU load time (which is probably leading to glitches). Stack analysis shows that this time is spent on synchronization (the process almost constantly hangs inside "ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x682"). These symptoms are treated by restarting the computer - after that, everything is fine for a while (the studio starts, compiles, the processor is loaded in normal mode, i.e. spending 10-15% of the time in the nucleus).
I would like to know if anyone else has this problem and what to do about it.
Please do not offer to reinstall the studio / Windows.

Answer 1

Maybe something with drivers or system services? a simple number-bite process is unlikely to hang the core. Also, check if there is enough memory and if the computer is not swapping. Also, try procmon, see what's going on in the system. Also, you can try the API Monitor program, which shows system calls. Procmonа process explorer and API monitor I recommend if you want to figure it out.
For music to stutter under Windows, the computer needs to be tortured very much, this almost never happens.

Answer 2

I don’t know how with VS 2010, but 11 beta generally puts the computer on the shoulder blades, as I understand it, some process switches to real-time priority and loads the percentage by 100%, the computer hangs up dead, approximately, what Intellisence does, because it happens sometimes before the prompt appears. I didn’t really understand it, but deleted it and returned to VS2010. And VS2010 seems to work fine.

Answer 3

Do you have any problems with the HDD?

Answer 4

Once faced with a similar problem. After a lot of googling, I found advice - delete all breakpoints via Debug -> Delete All BreakPoints. It worked for me, it might solve your problem too.

Answer 5

I remember having freezes due to IntelliTrace. Disabled - debugging has become faster, perhaps you have something to do with this.

Answer 6

ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel

Well, it's definitely NOT Visual Studio ITSELF. Presumably some kind of very smart filter / minifilter (probably an antivirus: like it needs a processor to check the signal). Try to collect a trace profile with stacks and see who captures these same spinlocks.