wrapped C/C++ object of type QgsRasterLayer has been deleted
Sometimes when new maps are added via drag&drop the following error occurs. It only happens when a layer has been added before or has been removed. It never happens when a first raster dataset is added.
Traceback (most recent call last):
File "C:/Users/m.wocher/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\enmapboxplugin\enmapbox\gui\datasourcemanager.py", line 1434, in dropMimeData
added.extend(self.dataSourceManager.addSource(url))
File "C:/Users/m.wocher/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\enmapboxplugin\enmapbox\gui\datasourcemanager.py", line 224, in addSource
knownStrings = self.uriList() + self.layerIds() + self.layerSources()
File "C:/Users/m.wocher/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\enmapboxplugin\enmapbox\gui\datasourcemanager.py", line 187, in layerSources
return [ds.mapLayer().source() for ds in self.sources() if isinstance(ds, DataSourceSpatial)]
File "C:/Users/m.wocher/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\enmapboxplugin\enmapbox\gui\datasourcemanager.py", line 187, in
return [ds.mapLayer().source() for ds in self.sources() if isinstance(ds, DataSourceSpatial)]
RuntimeError: wrapped C/C++ object of type QgsRasterLayer has been deleted
Comments (4)
-
-
reporter Hi, i’m sorry but I can’t. The error occurs sponaneously but frequently. Sometimes new raster data can be added, sometimes not. The only situation when it does not occur, is when a first dataset is added.
-
-
assigned issue to
-
assigned issue to
-
reporter - changed status to resolved
Hi, I think I found the reason for the error: It might have been caused by an error within the installation of the numba package.
The Enmap-Box (and also "import numba" in console) threw this error on startup: TypeError: create_target_machine() got an unexpected keyword argument 'jitdebug'
A rollback of the llvmlite package solved this error, as described here: https://github.com/rapidsai/cuml/issues/2389
python3 -m install -U llvmlite==0.32.1
- Log in to comment
I also had that problem from time to time. Matthias, can you give a step by step instruction to reproduce this error?