Quick growth of memory consumption (renderer to blame)

Bug #167394 reported by Bug Importer
0
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
Critical
Mental-users

Bug Description

Working on a simple Logo ( a few circles, user defined
curved lines, texts aligned to lines). If I change
anything at a line to which a text is aligned the
memory consumption of Inscape increases extremely.
Almost small changes let increase the memory usage from
30MB to 149MB.
A few changes later and all of my free memory is used
by Inscape. The memory usage window of Inkscape only
shows a small increas from 2MB to 3MB. I observed this
behaviour on three different WinXP Prof. Computers, and
it happened also with other graphics too.

My Hardware:
1. Intel Centrino Notebook 1,5GHz
   WinXP Prof.
   512MB RAM

2. AMD64, 3500+
   2GB Ram
   WinXP Prof.

Revision history for this message
Mental-users (mental-users) wrote :

Hmm, I can't replicate this on Linux with SVN trunk
(admittedly, I don't have a windows machine to try it on).
It seems to hover around ~30 to ~40 MB as I make changes.

On windows, the memory usage dialog currently only displays
statistics for libgc (getting statistics for the built-in
malloc is tricky), so most of that memory must be coming
from either standard malloc or possibly GDI resources.

Can someone with a WinXP machine try this with SVN trunk and
see what happens?

Revision history for this message
Bug Importer (bug-importer) wrote :

I tryed the same graphic under Open-Suse 10 with the same
result. But this time the increasing memory allocation of
the program was shown in the memory usage dialog too
(standard malloc increased extremely).
I do not have any experiences in using svn, so I am not able
to check the latest developer version.
If is there way to add the svg-file to a comment, please let
me know. Because it should be easier to see the problem.

Revision history for this message
Mental-users (mental-users) wrote :

You're only allowed to attach files to bug reports if you
log in. Logging when reporting/commenting on bugs in is a
good idea anyway (e.g. it's easier to contact you with
additional questions).

If you've not got a sourceforge account, it's not hard to
sign up. But in the meantime step-by-step isntructions for
creating a file which exhibits the problem would be good too.

Revision history for this message
Svenf (svenf) wrote :

Well, try following to reproduce the problem:

create a bezier curve (two points are enough). change the
bending of the curve at each point (with option: make node
symmetric). then create a text and put it to the line. If
you start to change the bending of the curve on witch the
text is putted you should see that the memory usage of
inkscape increases with each change. Tested on SUSE LINUX 10
(64bit version) and WinXP (32bit) and Inkscape 0.43.2.

Revision history for this message
Bug Importer (bug-importer) wrote :

I observe the same behaviour on Linux (Ubuntu Dapper RC1)
with Inkscape 0.43. Put some text on a path, move the path
and memory consumption shoots up, from 30 MB to about 200 MB
and growing.

Revision history for this message
Bug Importer (bug-importer) wrote :

Have same problem with Inkscape 0.44 pre3 on WindowsXP

Revision history for this message
Buliabyak-users (buliabyak-users) wrote :

Originator: NO

I replicated svenf's steps on 0.45. It starts at about 10% memory usage
and grows by almost 2% ater every nodeedit of the curve.

However if I do this in outline mode in SVN (which uses cairo) the memory
growth is much much smaller, maybe 0.1% per every several actions, probably
spent on undo. So this is obviously a problem with our renderer and it will
be fixed by the move to cairo.

ScislaC (scislac)
Changed in inkscape:
status: New → Confirmed
Revision history for this message
Krzysztof Kosinski (tweenk) wrote :

I can confirm that this issue does not appear in current SVN. I think the status can be changed to "Fix Committed".

Changed in inkscape:
status: Confirmed → Fix Committed
Ryan Lerch (ryanlerch)
Changed in inkscape:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.