Bug 307797 - KML Memory leak
Summary: KML Memory leak
Status: REPORTED
Alias: None
Product: marble
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: marble-bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-03 21:34 UTC by payam416
Modified: 2021-04-07 12:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description payam416 2012-10-03 21:34:05 UTC
I have built Marble Widget within my QT application. I am using version 0.12 of the source code. It seems as though there is memeory leak happening when I add a rather large KML file. The program memory used seems to grow without bound. 

Here is how I add the KML file:

QFileInfo inputFile( "WorldBorders.kml"); 
m->model()->addGeoDataFile(inputFile.absoluteFilePath()); 

kml file: http://code.google.com/p/kml123/downloads/detail?name=World%20Borders.kml

Also, as per http://forum.kde.org/viewtopic.php?f=217&t=108027&p=251448#p251448:

Earthwings : "I just did the following:

    Open marble with --enableFileView parameter
    Note memory usage
    Open http://code.google.com/p/kml123/downloa ... orders.kml
    Toggle checkbuttons in the file view tab, watch memory usage
    Close .kml file in the file view tab, note memory usage


Memory was ever increasing and didn't go down after closing the file, so I'd say you're right that there is a memory leak, or at least the .kml file is kept in memory even when it is not needed anymore."
Comment 1 Illya Kovalevskyy 2014-12-13 20:06:39 UTC
I am doing bug triaging as Google Code-In 2014 student.

IIRC current marble master doesn't have any memory leaks in KML implementation, valgrind shows the same.
Comment 2 sourcemaker 2020-10-30 01:27:26 UTC
Memory leak still exists.
Comment 3 sourcemaker 2021-04-07 12:47:21 UTC
Marble Virtual Globe
Version 2.2.20 

KDE Frameworks 
Version 5.80.0

As soon as the 8 GB memory is used up, the application crashes.