I doubt the sleep issue too
I really doubt that most CPUs are really sleeping the full 15mS anyway.
Every time there is an interrupt (mouse wiggle, network packet, end of video frame,...) the CPU has to wake up to process it.
If the timer is just being woken up to service Chrome, then it should be going to sleep again fast.
Sure there are some corner conditions (ie. no network, no mouse activity) when this bug might have been causiung a few % change in power usage, but that would be the exception and you can understand why the developers would give this a low priority.
Biting the hand that feeds IT
