Version: unspecified (using Devel) OS: Linux When running Marble through valgrind, I found that Marble is leaking many GeoNode objects, for example: ==16890== 23,278 (40 direct, 23,238 indirect) bytes in 1 blocks are definitely lost in loss record 4,309 of 4,315 ==16890== at 0x4C24DFA: operator new(unsigned long) (vg_replace_malloc.c:261) ==16890== by 0x54039A8: Marble::dgml::DgmlPropertyTagHandler::parse(Marble::GeoParser&) const (DgmlPropertyTagHandler.cpp:51) ==16890== by 0x53E0B19: Marble::GeoParser::parseDocument() (GeoParser.cpp:145) ==16890== by 0x53E0B93: Marble::GeoParser::parseDocument() (GeoParser.cpp:172) ==16890== by 0x53E0B93: Marble::GeoParser::parseDocument() (GeoParser.cpp:172) ==16890== by 0x53E0B93: Marble::GeoParser::parseDocument() (GeoParser.cpp:172) ==16890== by 0x53E0CCD: Marble::GeoParser::read(QIODevice*) (GeoParser.cpp:94) ==16890== by 0x547E931: Marble::MapThemeManager::loadMapThemeFile(QString const&) (MapThemeManager.cpp:136) ==16890== by 0x547EA37: Marble::MapThemeManager::loadMapTheme(QString const&) (MapThemeManager.cpp:119) ==16890== by 0x547F87F: Marble::MapThemeManager::mapThemes() const (MapThemeManager.cpp:86) ==16890== by 0x5451EF4: Marble::TileLoader::updateTextureLayers() (TileLoader.cpp:177) ==16890== by 0x5493D70: Marble::TextureLayer::Private::Private(Marble::MapThemeManager*, Marble::HttpDownloadManager*, Marble::SunLocator*, Marble::TextureLayer*) (TextureLayer.cpp:70) When I set DUMP_GEONODE_LEAKS to 1 I get: Found 196895 GeoNode object LEAKS! marble(16936)/kparts KParts::Part::~Part: deleting widget Marble::ControlView(0x1ef30d0) "" Found -19 GeoNode object LEAKS! Found -112 GeoNode object LEAKS! Found -31 GeoNode object LEAKS! Found -42 GeoNode object LEAKS! Found -429 GeoNode object LEAKS! Found -123 GeoNode object LEAKS! Found -2301 GeoNode object LEAKS! Found -193614 GeoNode object LEAKS! Found -6 GeoNode object LEAKS! Found -6 GeoNode object LEAKS! Michael Reproducible: Always
Somehow the version information went missing, but I get these leaks in both 4.6 and in trunk. Michael
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.