If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

svg rendering takes up huge amounts of ram

RESOLVED INCOMPLETE

Status

()

Core
SVG
RESOLVED INCOMPLETE
11 years ago
10 years ago

People

(Reporter: Florian Schnabel, Unassigned)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4

I made a webpage with a list, every entry got a language so i decided to view a tiny flag next to it.
The list currently got about 400 entrys, when using SVG (with iframe-tag) opening firefox and displying that one page took up about 120 MB of ram.
Since those are flags there were only 5 different images, the US-flag made up about 95% of images displayed.
As a reference: the same page with the same image sizes as .gif took up 23 MB ram.

Reproducible: Always

Comment 1

11 years ago
Testcase?
Component: General → SVG
Product: Firefox → Core
Version: unspecified → Trunk

Comment 2

11 years ago
afaik there is a lot of work going on to reduce the memory usage.
but remember, as opposed to raster images, for any instance of an SVG, a complete DOM has to be build and kept in memory. so naturally the RAM usage will allways be higher than for rasters.
(Reporter)

Comment 3

11 years ago
of course .. the svg is even 4x the size of the gif already ...
but about 100 extra MB ram for 400 images (350 of those being the same pic over and over again, just to remind you) is not really nice.
also it slows scrolling on a sempron 3400+ considderably ^^

Comment 4

11 years ago
check my last comment here:
https://bugzilla.mozilla.org/show_bug.cgi?id=276431#c28
i think resolving that bug would solve your problem , too.
Assignee: nobody → general
QA Contact: general → ian
There isn't much point in keeping this bug open in its current state. We know we have general issues with memory usage, but this bug doesn't reference any specific testcase for us to focus on, so it's not useful. If you provide a specific example for us to work on, Florian, then great. Otherwise I'm going to close this as INCOMPLETE for now. That doesn't mean we won't be working on memory usage. We will.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.