mod->set_param_string memory leak
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Triaged
|
Medium
|
Unassigned |
Bug Description
Valgrind shows a small memory leak associated with calling mod->set_
emf_print_
==21262== 16 bytes in 1 blocks are definitely lost in loss record 7,095 of 20,681
==21262== at 0x402BE68: malloc (in /usr/lib/
==21262== by 0x8502DBE: Inkscape:
==21262== by 0x8502EAE: Inkscape:
==21262== by 0x8343420: Inkscape:
==21262== by 0x80DCD82: Inkscape:
==21262== by 0x81F74A9: Inkscape:
==21262== by 0x824EB76: Inkscape:
==21262== by 0x81FB006: Inkscape:
==21262== by 0x81F99CF: Inkscape:
==21262== by 0x80AF67E: _ZL9file_
==21262== by 0x80AF0CE: sp_file_
==21262== by 0xBD2C48B: ???
The call(s) that triggered this were in my EMF code, in lines copied verbatim from this file:
latex-pstricks-
latex-pstricks-
It looks like there should be some sort of release_
tags: | added: performance |
Changed in inkscape: | |
importance: | Undecided → Medium |
status: | New → In Progress |
With revision 11646, some memory leaks should have been fixed. Could you have a look whether it solves this issue?