Hi!
Does ESRI know that there is a memory Leak using
ESRI::ArcGISTiledLayer, ESRI::Basemap (V100.5 and V100.6))
Creating and destroing a simple map WITHOUT terminating the application.
Valgrind (@V100.5)
class ESRI::ArcGISTiledLayer
==24614== 15,592 (1,744 direct, 13,848 indirect) bytes in 1 blocks are definitely lost in loss record 835 of 855
==24614== at 0x4C2E2AF: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==24614== by 0x40F5E69: operator new(unsigned long) (in /usr/lib64/libc++.so.1.0)
==24614== by 0xA877D11: ??? (in /usr/lib64/libruntimecore.so)
==24614== by 0xA1FF237: RT_ImageTiledLayer_create (in /usr/lib64/libruntimecore.so)
==24614== by 0x5206BE1: ESRI::RuntimeCore::QRTImageTiledLayer::QRTImageTiledLayer() (in /usr/lib64/libEsriCommonQt.so)
==24614== by 0x525969C: ESRI::RuntimeCore::QRTArcGISTiledLayer::QRTArcGISTiledLayer(ESRI::RuntimeCore::QRTTileCache*) (in /usr/lib64/libEsriCommonQt.so)
==24614== by 0x55BCC65: QRTImpl::ArcGISTiledLayerImpl::ArcGISTiledLayerImpl(std::shared_ptr<QRTImpl::TileCacheImpl> const&) (in /usr/lib64/libEsriCommonQt.so)
==24614== by 0x49A566: Esri::ArcGISRuntime::ArcGISTiledLayer::ArcGISTiledLayer(Esri::ArcGISRuntime::TileCache*, QObject*) (in /shd/CTC/TOOLS/LTS-Esri-SupportDir/LTS-Esri/Prepared/LayerMemoryLeak/LayerMemoryLeak)
==24614== by 0x498C34: MapWindow::MapWindow() (in /shd/CTC/TOOLS/LTS-Esri-SupportDir/LTS-Esri/Prepared/LayerMemoryLeak/LayerMemoryLeak)
==24614== by 0x4971CA: main (in /shd/CTC/TOOLS/LTS-Esri-SupportDir/LTS-Esri/Prepared/LayerMemoryLeak/LayerMemoryLeak)
class ESRI::Basemap
(just the main leaks of ESRI::Basemap)
==24614== 4,288 bytes in 8 blocks are still reachable in loss record 806 of 855
==24614== at 0x4C2E2AF: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==24614== by 0x40F5E69: operator new(unsigned long) (in /usr/lib64/libc++.so.1.0)
==24614== by 0xC43FB01: ??? (in /usr/lib64/libruntimecore.so)
==24614== by 0xC43A737: ??? (in /usr/lib64/libruntimecore.so)
==24614== by 0xC43A2A2: ??? (in /usr/lib64/libruntimecore.so)
==24614== by 0xC44343C: ??? (in /usr/lib64/libruntimecore.so)
==24614== by 0xC442110: ??? (in /usr/lib64/libruntimecore.so)
==24614== by 0xA07D9D4: RT_ArcGISRuntimeEnvironment_setInstallDirectory (in /usr/lib64/libruntimecore.so)
==24614== by 0x5255D74: ESRI::RuntimeCore::QRTArcGISRuntimeEnvironment::setInstallDirectory(QString const&, ESRI::RuntimeCore::QRTObject*) (in /usr/lib64/libEsriCommonQt.so)
==24614== by 0x56C1574: QRTImpl::ArcGISRuntimeEnvironmentImpl::initialize() (in /usr/lib64/libEsriCommonQt.so)
==24614== by 0x4A21CD: Esri::ArcGISRuntime::Basemap::Basemap(QObject*) (in /shd/CTC/TOOLS/LTS-Esri-SupportDir/LTS-Esri/Prepared/LayerMemoryLeak/LayerMemoryLeak)
==24614== by 0x4985B4: MapWindow::MapWindow() (in /shd/CTC/TOOLS/LTS-Esri-SupportDir/LTS-Esri/Prepared/LayerMemoryLeak/LayerMemoryLeak)
==24614==
==24614== 4,288 bytes in 8 blocks are still reachable in loss record 807 of 855
==24614== at 0x4C2E2AF: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==24614== by 0x40F5E69: operator new(unsigned long) (in /usr/lib64/libc++.so.1.0)
==24614== by 0xC43FB01: ??? (in /usr/lib64/libruntimecore.so)
==24614== by 0xC43A737: ??? (in /usr/lib64/libruntimecore.so)
==24614== by 0xC43A2DF: ??? (in /usr/lib64/libruntimecore.so)
==24614== by 0xC44343C: ??? (in /usr/lib64/libruntimecore.so)
==24614== by 0xC442110: ??? (in /usr/lib64/libruntimecore.so)
==24614== by 0xA07D9D4: RT_ArcGISRuntimeEnvironment_setInstallDirectory (in /usr/lib64/libruntimecore.so)
==24614== by 0x5255D74: ESRI::RuntimeCore::QRTArcGISRuntimeEnvironment::setInstallDirectory(QString const&, ESRI::RuntimeCore::QRTObject*) (in /usr/lib64/libEsriCommonQt.so)
==24614== by 0x56C1574: QRTImpl::ArcGISRuntimeEnvironmentImpl::initialize() (in /usr/lib64/libEsriCommonQt.so)
==24614== by 0x4A21CD: Esri::ArcGISRuntime::Basemap::Basemap(QObject*) (in /shd/CTC/TOOLS/LTS-Esri-SupportDir/LTS-Esri/Prepared/LayerMemoryLeak/LayerMemoryLeak)
==24614== by 0x4985B4: MapWindow::MapWindow() (in /shd/CTC/TOOLS/LTS-Esri-SupportDir/LTS-Esri/Prepared/LayerMemoryLeak/LayerMemoryLeak)
and some more
I am already in contact with the support team, but no real progress ...