Memory leak in Convert Object to Path

Bug #1277036 reported by suresh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
Undecided
Unassigned

Bug Description

Hi,

I have created a tool called 'Memwatch' which prints the memory usage. More info found on below link.
https://github.com/skanzariya/Memwatch

I use this tool to find where memory leak in Inkscape. I found most memory leak while converting Object into Path. I am set the break point at function 'sp_selected_path_to_curves' and step into the code and in backend I start Memwatch, I found most of memory leak in this function.

'sp_selected_path_to_curves' further call another function in which object convert object into path using function curve.cpp, I also found in function 'sp_item_list_to_curves' when the repr append to the parent (parent->appendChild(repr)) it takes memory which no release further. So It will be great if some one can look into the code to fix the leak.

Thanks.

Revision history for this message
suresh (suresh-meetsme) wrote :

Guys,

Is this bug confirmed?

Revision history for this message
suresh (suresh-meetsme) wrote :

Hello @Suv,

is there any updates on this? is there any development on this? please update so that i can test the same.

Revision history for this message
su_v (suv-lp) wrote :

> is there any updates on this?

No - otherwise the bug status would have been updated, and/or a comment added.

> is there any development on this?

No - otherwise the bug status would have been updated, and/or a comment added.

> please update so that i can test the same.

There is nothing to update to the best of my knowledge.

Revision history for this message
suresh (suresh-meetsme) wrote :

Updates...

Memork keeps increase while converting text into path.

Here is my scenario.
1. Write any text
2. Convert text into path using Object to Path.
3. Repeat the above step again and again with different text and watch the memory usage by Memwatch.

Here is mine.
 Total Ram Application Percentage
   2027152kB 80572kB 3.975%
   2027152kB 81136kB 4.002%
   2027152kB 81712kB 4.031%
   2027152kB 82508kB 4.070%
   2027152kB 83224kB 4.105%
   2027152kB 83508kB 4.119%
   2027152kB 83552kB 4.122%
   2027152kB 83728kB 4.130%
   2027152kB 83756kB 4.132%
   2027152kB 83768kB 4.132%
   2027152kB 84168kB 4.152%
   2027152kB 84168kB 4.152%
   2027152kB 84168kB 4.152%
   2027152kB 84168kB 4.152%
   2027152kB 84332kB 4.160%
   2027152kB 84336kB 4.160%
   2027152kB 85936kB 4.239%
   2027152kB 85936kB 4.239%
   2027152kB 85980kB 4.241%
   2027152kB 85992kB 4.242%
   2027152kB 86016kB 4.243%
   2027152kB 86016kB 4.243%
   2027152kB 86020kB 4.243%
   2027152kB 86020kB 4.243%
   2027152kB 86064kB 4.246%
   2027152kB 86064kB 4.246%
   2027152kB 86104kB 4.248%
   2027152kB 86104kB 4.248%
   2027152kB 86104kB 4.248%
   2027152kB 86136kB 4.249%
   2027152kB 86208kB 4.253%
   2027152kB 86208kB 4.253%
   2027152kB 86260kB 4.255%
   2027152kB 86260kB 4.255%
   2027152kB 86260kB 4.255%
   2027152kB 86260kB 4.255%
   2027152kB 86260kB 4.255%
   2027152kB 86260kB 4.255%
   2027152kB 86268kB 4.256%
   2027152kB 86268kB 4.256%
   2027152kB 86268kB 4.256%
   2027152kB 86268kB 4.256%
   2027152kB 86268kB 4.256%
   2027152kB 86272kB 4.256%
   2027152kB 86428kB 4.264%
   2027152kB 86444kB 4.264%
   2027152kB 86616kB 4.273%
   2027152kB 86616kB 4.273%
   2027152kB 86616kB 4.273%

I did the above steps 7-8 times and huge memory increase.

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.