Bug 1299222 - Memory leak in inkscape with matplotlib svg file
Memory leak in inkscape with matplotlib svg file
Product: Fedora
Classification: Fedora
Component: inkscape (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Gwyn Ciesla
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-01-17 09:11 EST by Yann Briheche
Modified: 2016-12-20 12:57 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 12:57:29 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Sample file producing memory leak (620.49 KB, image/svg+xml)
2016-01-17 09:11 EST, Yann Briheche
no flags Details
Sample file with lower miterlimit (no memory leak in that case) (613.41 KB, image/svg+xml)
2016-01-17 09:12 EST, Yann Briheche
no flags Details

  None (edit)
Description Yann Briheche 2016-01-17 09:11:15 EST
Created attachment 1115607 [details]
Sample file producing memory leak

Description of problem:
Memory leak occurs in inkscape when using svg files with a high stroke-miterlimit parameter (for example, generated by matplotlib >=1.5.1). It seems it is caused by a bug in inkscape renderer (see additional info for more details)

I attached some samples :
-sample_miterlimit100000_memoryleak.svg is the original file with miterlimit of 100000. The memory leak occurs on opening, and fills my 8GB ram in few seconds.
-sample_miterlimit10_nomemoryleak.svg is the same file I edited and set every value of miterlimit to 10. No memory leak occurs (inkscape RAM usage stays under 300MB no matter what I do)

Version-Release number of selected component (if applicable):
inkscape 0.91 rev13725 15.fc23 x86_64

How reproducible:

Steps to Reproduce:
1.Open sample file sample_miterlimit100000_memoryleak.svg
2.Zoom in zoom out

Actual results:
Memory leak
Inkscape freezes
Expected results:

Additional info:
It was referenced and confirmed on inkscape rev13725 on inkscape bug tracker.
It was apparently fixed in rev13966

Current inkscape package on f23 and rawhide is rev13725, and is afflicted with said bug.
Updating to a recent revision should fix this.
Comment 1 Yann Briheche 2016-01-17 09:12 EST
Created attachment 1115608 [details]
Sample file with lower miterlimit (no memory leak in that case)
Comment 2 Fedora End Of Life 2016-11-24 10:00:21 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Fedora End Of Life 2016-12-20 12:57:29 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.