InkScape memory leak issue

Bug #1022438 reported by suresh
This bug report is a duplicate of:  Bug #1061967: memory problems reported by valgrind. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
Undecided
Unassigned

Bug Description

Hi,

I compiled inkscape for ARM platform and install to the board. It is running very well, but with some simple drawing it takes a time for rendering. When i try to render an object CPU increase upto 78%.

I draw a simple drawing and run inkscape overnight and in morning, Below is the top command status where VSZ increase upto 28% from 11%. When i finished the drawing VSZ was 11% and in morning it increase upto 28%.

I googling and found that VSZ increase if software has a memory leak. I run valgrind for inkscape running in my ubuntu and found several memory leak.

Mem: 387192K used, 539912K free, 0K shrd, 6548K buff, 107768K cached
CPU: 0% usr 0% sys 0% nic 99% idle 0% io 0% irq 0% sirq
Load average: 0.05 0.05 0.05 1/60 1689
  PID PPID USER STAT VSZ %VSZ %CPU COMMAND
 1168 1167 root S 253m 28% 0% /root/inkscape
  664 1 root S 61840 7% 0% X :0 -nolisten tcp vt7 -quiet -novtswi

Let me know if you require further data for analyze the problem.

Tags: memory
Revision history for this message
Gorenko Roman (grk26331) wrote :

Mmmm... Deleaker or Valgrind... Problem is solved :)

Revision history for this message
nightrow (jb-benoit) wrote :

So, can we solve this ?
What would be usefull ?
Or is this to be sorted as invalid ?

Revision history for this message
Kris (kris-degussem) wrote :

Certainly not invalid. There is a lot of work to do, although it is not immediately definable what to do.
I plan to do some work on this if I can get my setup working again and if 0.49 is out.

I propose to mark this bug as duplicate of Bug #1061967 which contains a valgrind memory check log.

Revision history for this message
ScislaC (scislac) wrote :

Kris: Trunk will remain trunk, so as long as you're keeping your local copy up to date and don't commit anything related to this prior to 0.49 branching, all is well. (just saying 0.49 shouldn't impact you)

Revision history for this message
Kris (kris-degussem) wrote :

Marking as duplicate of Bug #1061967, per comment 3.

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.