Is there a reason why CPU usage will jump when debugging in Word VBA?
I noticed that even when I "step into" a project, and nothing is actually being calculated except waiting for me to step to the next statement, the CPU goes up about 25-30% and stays there, across all 4 cores on a Core-i5 2400.
I can verify in Task Manager that WINWORD.EXE is the culprit. Memory use is consistent and expected. CPU usage up almost 30%, and it immediately drops off if I stop debugging.
This is in Office 2007.