Bug report #15064
QGIS crashes on OGR layers with wkbUnknown25D, wkbUnknownM/Z/ZM layer geometry type
Status: | Closed | ||
---|---|---|---|
Priority: | Severe/Regression | ||
Assignee: | Even Rouault | ||
Category: | Data Provider/OGR | ||
Affected QGIS version: | master | Regression?: | No |
Operating System: | Easy fix?: | No | |
Pull Request or Patch supplied: | No | Resolution: | fixed/implemented |
Crashes QGIS or corrupts data: | No | Copied to github as #: | 23007 |
Description
Such layers can be found in GeoPackage datasets.
Associated revisions
QgsRendererV2PropertiesDialog::syncToLayer(): make it robust to NULL renderer
Fixes #15064
Probably just a band-aid, proper fix to follow in OGR provider itself.
[OGR provider] Do not return wkbUnknown25D, wkbUnknownM/Z/ZM layer geometry types
Those are illegal QgsWKBTypes::Type / QGis::WkbType values, and can cause
undefined behaviour outside of the provider.
Fixes #15064
[OGR provider] Do not return wkbUnknown25D, wkbUnknownM/Z/ZM layer geometry types
Those are illegal QgsWKBTypes::Type / QGis::WkbType values, and can cause
undefined behaviour outside of the provider.
Fixes #15064
History
#1 Updated by Even Rouault over 8 years ago
- Status changed from Open to Closed
Fixed in changeset 7b7c3773d87f07307cac2666c18faa0a611fe9cb.
#2 Updated by Even Rouault over 8 years ago
- Target version set to Version 2.14
- Status changed from Closed to In Progress
#3 Updated by Even Rouault over 8 years ago
- Resolution set to fixed/implemented
- % Done changed from 0 to 100
#4 Updated by Even Rouault over 8 years ago
- Status changed from In Progress to Closed