854024 - Filter heavy SVG MediaWiki logo renders more slowly than in Chrome

Status: RESOLVED WORKSFORME

(Core :: SVG, defect)

Description

[Patrick Storz]

Attachment: The sample SVG file that renders slowly

Firefox's SVG rendering speed is alarmingly poor on this SVG image (MediaWiki's logo):
http://upload.wikimedia.org/wikipedia/commons/5/54/MediaWiki_logo_1.svg

Firefox gets totally unresponsive on my hardware while trying to render the SVG so i have to kill the process. Even after minutes the file isn't rendered completely.

I compared it to other SVG renderers available to me at the moment, all of which are substantially faster:
- Inkscape renders the file without problems within seconds and keeps responsive (zooming, etc.) all the time
- rsvg-convert takes ~ 10 s to render the file in it's native size
- even Internet Explorer renders the file within ~ 10 s with only some small lags and without obvious rendering errors

I tried rendering on my machine with hardware acceleration switched on (I've got an ATI Mobility Radeon HD 3470) as well as switched off, without a notable difference.

Comment 1

[Robert Longson [:longsonr]]

Renders about the same speed as Opera for me which is around 10 seconds, same as you've seen with other tools.

Comment 2

[Loic]

I'm able to observe the hang too, with HWA disabled, it's more responsive (even lag is still present).

Comment 3

[(mostly gone) XtC4UaLL [:xtc4uall]]

svg.display-lists.painting.enabled;false set makes some Differences too.

Comment 4

[Jonathan Watt [:jwatt]]

We are much slower than Chrome on Mac, especially when doing things like resizing the window and mousing over the page.

For the initial paint I'm seeing:

60% of the time under nsSVGIntegrationUtils::PaintFramesWithEffects
15% creating and processing display list items

There are 19731 display elements (including filters, gradients, groups, etc).

When mousing over the content, I'm seeing lots of long pauses, and over 60% of the time being spent building display lists.

Comment 5

[Jonathan Watt [:jwatt]]

Still more than two thirds of the time handling filters despite the filter improvements the last few years, and still noticeably slower than Chrome.

https://perfht.ml/2nKXVJe

Comment 6

[Robert Longson [:longsonr]]

Seems OK now.