The problem is that a memory-read on a bad address causes a bus fault error. A bus fault error looks just like a "memory-read not done" to the debugger's polling routine. So the polling routine must time-out before it can terminate. This time-out takes a long time, resulting in very slow window update speeds. The solution is to scroll the window so that bad memory is not visible.