799663 - High CPU usage on SVG animations

Status: RESOLVED FIXED

(Core :: SVG, defect)

Description

[ed.rooth]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.79 Safari/537.4

Steps to reproduce:

Vist any website that has complex SVG animation. 
Such as: 
http://mbostock.github.com/d3/talk/20111116/force-collapsible.html


Actual results:

CPU instantly spikes to 100%, animations are slow and jagged.


Expected results:

Should behave more like Chrome/Safari. Smoother faster animations. CPU usage is moderate, rarely goes about 50%-80%.

Comment 1

[Robert Longson [:longsonr]]

Have you tried Firefox 18 Aurora? Is it better there?

Comment 2

[ed.rooth]

I tried Firefox 17 Aurora and the latest nightly (Aurora 19). Both exhibit the same behavior.

I did not try Firefox 18 Aurora b/c I couldn't find a link to download it.

Comment 3

[Jonathan Watt [:jwatt]]

I don't see any issues with latest Nightly. Can you retest, please?

Comment 4

[Jonathan Watt [:jwatt]]

I do see high CPU usage, actually.

This example just moves lots of circles around by changing their cx/cy attributes, and lots of lines by changing their x1/y1/x2/y2 attributes. So really this mostly depends on us drawing faster. Implementing Quartz content on Mac will hopefully help reduce CPU usage here.

Comment 5

[Cornel Ionce [:noni] [Hubs QA]]

Mozilla/5.0 (X11; Linux i686; rv:26.0) Gecko/20100101 Firefox/26.0
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:26.0) Gecko/20100101 Firefox/26.0
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0

This behavior also reproduces on Firefox 26 beta 7 (Build ID: 20131122094025) for the following URL's:

- http://www.carto.net/papers/svg/samples/jumping_cubes.svg
- http://svg.kvalitne.cz/worldlandmarks/worldlandmarks.svg
- http://svg-wow.org/audio/animated-lyrics.svg

Animations are very slow and the CPU load is extremely high.
Marking as NEW.

Comment 6

[Jonathan Watt [:jwatt]]

I think once bug 1090934 is fixed we can probably just call this done.

Cornel, regarding comment 5, those should be filed as separate bugs.