Context Navigation

Changes between Initial Version and Version 1 of Ticket #967, comment 4

-                      initial
+                      v1
 identify video: most=100% damage count={R(0, 79, 2098, 1306): MutableInteger(400)}
 }}}
 So it finds that 100% of screen updates happen in the region that previously identified as video, that's roughly 400 repaints per second! (the calculations run at most every second - less when there is not much happening on screen)
+So it finds that 100% of screen updates happen in the region that previously identified as video, that's roughly 20 to 40 repaints per second! (the calculations run at most every second - less when there is not much happening on screen)
 Not only that, but if you look at the actual paint events themselves (the format is simple: {{{timestamp, X, Y, WIDTH, HEIGHT}}}), ie:
 …
 I found a good page which explains the browsers' rendering process: [http://www.html5rocks.com/en/tutorials/internals/howbrowserswork/ How Browsers Work: Behind the scenes of modern web browsers]
 If the problem comes from the browser's rendering engine rather than the page, this needs to be fixed as it will consume huge amounts of CPU for absolutely nothing.
+Edit: originally said 400 updates per second, which was incorrect. We keep the most recent 400 events, and the time difference from oldest to newest is roughly between 10 and 20 seconds.