| Summary: | Animation with a timing function property in a keyframe eats CPU | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> | ||||||
| Component: | CSS | Assignee: | Simon Fraser (smfr) <simon.fraser> | ||||||
| Status: | RESOLVED FIXED | ||||||||
| Severity: | Normal | CC: | cmarrin | ||||||
| Priority: | P2 | Keywords: | InRadar | ||||||
| Version: | 528+ (Nightly build) | ||||||||
| Hardware: | All | ||||||||
| OS: | OS X 10.5 | ||||||||
| Attachments: |
|
||||||||
Created attachment 33840 [details]
Patch, changelog
|
Created attachment 33839 [details] Testcase The attached demo eats about 22% of the CPU, even though only 10 things are animating. I attach a sample; most of it is under AnimationControllerPrivate::updateAnimationTimer(bool), which seems to be firing as fast as it can become some keyframe animation is returning 0 from timeToNextService().