Crash after calling QgsMapLayerRegistry::addMapLayers

[qgib]

Author Name: Giuseppe Sucameli (@brushtyler)
Original Redmine Issue: 5747
Affected QGIS version: master
Redmine category:python_plugins

---

The @QgsMapLayerRegistry.addMapLayer@ is deprecated but the newer version @QgsMapLayerRegistry.addMapLayers@ if called two times cause segfault.

From the python console:

vl1 = QgsVectorLayer("/home/brushtyler/vl1", "test", "ogr")
QgsMapLayerRegistry.instance().addMapLayers([vl1])

vl2 = QgsVectorLayer("/home/brushtyler/vl2", "test", "ogr")
QgsMapLayerRegistry.instance().addMapLayers([vl2])
</code>

Confirmed on both Win7 and Ubuntu 11.04, QGis 1.8

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

is this a regression since 1.7.4?

[qgib]

Author Name: Giuseppe Sucameli (@brushtyler)

---

Giovanni Manghi wrote:

is this a regression since 1.7.4?

no, the QgsMapLayerRegistry::addMapLayers() method is new in 1.8 (it wasn't present in 1.7.x)

[qgib]

Author Name: Larry Shaffer (Larry Shaffer)

---

Giuseppe,

I attempted to confirm with 1.8_1125571 on Mac OS X 10.6.8 and Ubuntu 12.04, but I couldn't get @QgsMapLayerRegistry.addMapLayers()@ to work without an exception being raised:

TypeError: QgsMapLayerRegistry.addMapLayers(list-of-QgsMapLayer, bool theEmitSignal=True): first argument of unbound method must have type 'QgsMapLayerRegistry'

I tried @from qgis.core import QgsMapLayerRegistry@ but ends in same exception.

However, I had no issues adding 7 layers with @QgsMapLayerRegistry.instance().addMapLayers()@, as long as I did not use an existing layer name as the second parameter to the @QgsVectorLayer@ constructor.

This works on both platforms:

v1 = QgsVectorLayer("/data/hr_100kdlg/hr-bnd.shp", "test1", "ogr")
QgsMapLayerRegistry.instance().addMapLayers([v1])
v2 = QgsVectorLayer("/data/hr_100kdlg/hr-rds.shp", "test2", "ogr")
QgsMapLayerRegistry.instance().addMapLayers([v2])
...
v7 = QgsVectorLayer("/data/hr_100kdlg/hr-quads.shp", "test7", "ogr")
QgsMapLayerRegistry.instance().addMapLayers([v7])
</code>

but this causes the crash on both platforms (sometimes took 3 layers):

v1 = QgsVectorLayer("/data/hr_100kdlg/hr-bnd.shp", "samename", "ogr")
QgsMapLayerRegistry.instance().addMapLayers([v1])
v2 = QgsVectorLayer("/data/hr_100kdlg/hr-rds.shp", "samename", "ogr")
QgsMapLayerRegistry.instance().addMapLayers([v2])
</code>

Does it still crash on your tested platforms when using dissimilar layer names in @QgsVectorLayer@ constructor?

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

• category_id was changed from Map Canvas to Python plugins

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

Fixed in changeset "d78e6052431192351115eac5720c34721a5085c1".

---

• status_id was changed from Open to Closed