I'm using the built in JS carousel a rotating header on my site. The problem occurs while using tabs in the latest version of Chrome.

First open a page with a carousel on it. Then open a new tab (same window). After a few slides would have gone by, switch back to the carousel. The current slide/next slide transition should be broken for one iteration. For example, the current slide image isn't shown until the next slide takes its place. Also the transition times seem to be off. After the one broken iteration, the carousel works as normal.

Maybe this is something that Chrome is doing to save CPU?