i have been wrestling with this for weeks, both professionally and personally. I'm fairly certain that in this process/before we noticed the problem we burned up one of our machines.
The thing is, there's no flash involved. We've narrowed it down to css3 transitions running amok. In other cases we've poorly constructed JS loops causing problems.
Recently i've noticed it on everything (even gmail, drive and calendar) in chrome.
No problems elsewhere, although in a side-by-side comparison with mozilla showed mozilla nearing similar cpu usage (30-60%) but never sustained (lasting seconds)
Not sure if this helps anyone, or if this is just 'duh.' The css3 transitions being involved i have not read out in the wild, so i thought i'd toss that idea out.
The thing is, there's no flash involved. We've narrowed it down to css3 transitions running amok. In other cases we've poorly constructed JS loops causing problems.
Recently i've noticed it on everything (even gmail, drive and calendar) in chrome.
No problems elsewhere, although in a side-by-side comparison with mozilla showed mozilla nearing similar cpu usage (30-60%) but never sustained (lasting seconds)
Not sure if this helps anyone, or if this is just 'duh.' The css3 transitions being involved i have not read out in the wild, so i thought i'd toss that idea out.