Bug 249883 - huge memory leak in Karbon when loading big svg file
Summary: huge memory leak in Karbon when loading big svg file
Status: RESOLVED WORKSFORME
Alias: None
Product: karbon
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Jan Hambrecht
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-02 13:00 UTC by Paweł
Modified: 2021-01-06 04:34 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paweł 2010-09-02 13:00:43 UTC
Version:           unspecified (using KDE 4.5.0) 
OS:                Linux

I am using Arch Linux, KDE 4.5.1 and Koffice 2.2.1. When I open very large svg file (about 26MB) Koffice becomes unresponsive and its memory usage rises slowly to more then 90% of entire memory present in my system and then swap file is being used too.  During the load of the file only one of two CPU cores is used by Karbon. When I open the same file in Konqueror (using webkit kde part) there's no memory leak at all.

Reproducible: Always

Steps to Reproduce:
Just try to open large svg file.

Actual Results:  
Exactly the same what I have wrote earlier.

Expected Results:  
It should load the image and be responsive.
Comment 1 Cyrille Berger 2010-10-03 12:15:33 UTC
Do you have a link to such a big SVG file ? I tried with a few big files I could find on the internet but they were like 1.8MB and worked well.
Comment 2 Paweł 2010-10-03 13:22:45 UTC
(In reply to comment #1)
> Do you have a link to such a big SVG file ? I tried with a few big files I
> could find on the internet but they were like 1.8MB and worked well.

Yes, here's the compressed file:

http://www.sendspace.pl/file/bfb0b9017ca56868e618dc9
Comment 3 Cyrille Berger 2010-10-03 13:48:09 UTC
Thanks I can confirm, and still happen in development version.
Comment 4 Cyrille Berger 2010-10-03 14:28:40 UTC
Well I couldn't open that file inkscape nor arora for memory problem as well. And in iceweasel it took about 600MB of memory. While konqueror/khtml didn't use so much memory but after 5 minutes of CPU usuage I didn't get any output.
Comment 5 Paweł 2010-10-03 14:38:28 UTC
Thanks for your responses. Did you try using Konqueror + webkit part (there's some tweaking needed to make Konqueror to use it)? It should also open in Firefox too. I read it opens in inkskape, but I didn't give it a try. However, if inkskape behaves similar then this isn't probably serious issue, because nobody operates on such huge files I guess. :)
Comment 6 Justin Zobel 2020-12-07 05:11:12 UTC
Thank you for the report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 7 Bug Janitor Service 2020-12-22 04:34:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2021-01-06 04:34:04 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!