Bug report #11062
Manipulating a cached WFS layer causes application crash
Status: | Closed | ||
---|---|---|---|
Priority: | Severe/Regression | ||
Assignee: | - | ||
Category: | Web Services clients/WFS | ||
Affected QGIS version: | 2.4.0 | Regression?: | No |
Operating System: | Windows | Easy fix?: | No |
Pull Request or Patch supplied: | No | Resolution: | not reproducable |
Crashes QGIS or corrupts data: | Yes | Copied to github as #: | 19396 |
Description
Also noted at: [http://gis.stackexchange.com/questions/110651/qgsmaplayerregistry-removemaplayerswfs-layer-causes-crash]
First I loaded a single WFS layer (from Geoserver) into QGIS 2.4 using the standard 'Add WFS layer' dialog, keeping the 'Cache features' option checked. Then in the Python console, typed the following code:
lyr = iface.legendInterface().layers()[0]
Then one of the following lines:
QgsMapLayerRegistry.instance().removeMapLayer(lyr.id()) # or: lyr.reload() # or: lyr.dataProvider().reloadData()
These cause a crash to desktop with no warnings, errors or dumps.
If I add a layer by unchecking the 'Cache features' option, none of the problems occur. I am also trying to add the the layer using pyqgis, and to work around this will probably have to insert a precalculated bbox parameter in the WFS url.
Related issues
History
#1 Updated by Matthias Kuhn about 10 years ago
- Target version set to Version 2.6
- Priority changed from Normal to Severe/Regression
#2 Updated by Jürgen Fischer almost 10 years ago
- Status changed from Open to Feedback
not reproducable here using the "USA Population" layer from the geoserver from osgeo live 7.0 with either QGIS 2.4 or master.
#3 Updated by Jürgen Fischer almost 10 years ago
- Target version changed from Version 2.6 to Future Release - High Priority
#4 Updated by Jürgen Fischer over 9 years ago
- Resolution set to not reproducable
- Status changed from Feedback to Closed
closing for the lack of feedback