315881 - SVG causes huge memory consumption

Status: RESOLVED FIXED

(Core :: SVG, defect)

Description

[Bart Friederichs]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

When opening the URL, the memory usage of X will grow to huge proportions (450MB or 90% of available memory).

Reproducible: Always

Steps to Reproduce:
1. Open URL http://www.friesoft.nl/adn.svg

Actual Results:  
X slows down.

Expected Results:  
Rendered SVG (or error message if used parts of the SVG or not implemented yet)

The SVG is written by myself, and renders correctly in Adobe SVG Viewer in both Linux (Firefox 1.0.7) and Windows (Internet Explorer 6). It uses a large amount of scripts, but they are not available in the testcase. When scripts are available, the same thing happens.

Because the system slows down, it is hard to find out what exactly the problem is.

Comment 1

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051109 Firefox/1.5 ID:2005110922

WFM. 

Comment 2

[Bart Friederichs]

Right. It works fine on Windows (though the scripts do not work; the changing of the Viewbox attribute doesn't. But that's another issue), it is Linux/X where it is not working.

Comment 3

[Andrew Schultz]

Attachment: testcase

This exhibits the bug with linux SeaMonkey trunk 20051111

  <rect width="15961.904" height="13461.905" />

The testcase isn't as bad as the whole page, but still makes things pretty sluggish.  It seems to mostly be X (not the app) that uses CPU.

Comment 4

[Andrew Schultz]

marking NEW

Comment 5

[jonathan chetwynd]

wfm
black screen in ~1sec

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

Comment 6

[Robert Longson [:longsonr]]

Is this still a problem with a trunk nightly on Linux?

Comment 7

[tor]

Attached testcase loads instantly and redraws fast on linux trunk.

Comment 8

[Andrew Schultz]

This got fixed by the cairo 1.5.x upgrade