I've noticed that, often, FDT gets into some state where it stops responding to user input for 1-2 seconds approximately every 25 seconds, like clockwork. There CPU is not busy when this happens. These freezes are extremely annoying as they stop the editor from responding often while I am in the middle of typing/navigating. If I shutdown and restart FDT, the freezes go away (temporarily). I've noticed that they typically appear during/after a debugging session.
Anyway, seeing as the CPU is not busy when these freezes occur, this really seems to be some kind of "wait" operation that is blocking the main input thread inappropriately.
Is there some internal FDT activity that could be blocking the main input thread every 25 seconds? Can it be moved to a background thread? Is the delay perhaps caused by a time-out value that should be set to zero?