Bug report #20932

Crash when running snap geometries to layer on large data set

Added by Andy Whyte almost 4 years ago. Updated almost 4 years ago.

Affected QGIS version:3.4.3 Regression?:No
Operating System:Windows 10 Easy fix?:No
Pull Request or Patch supplied:No Resolution:up/downstream
Crashes QGIS or corrupts data:Yes Copied to github as #:28751


I have a point layer with 2,365,043 features that I am trying to run the Snap geometries to layer algorithm on. Every time I run it QGIS crashes. I understand this is a very large file to work on but it should not crash QGIS.

The input and reference layer are the same and I am using a tolerance of 1 meter with the Prefer aligning nodes, don't insert new vertices option.

I have attached a Project file and here is a Dropbox link to the data - https://www.dropbox.com/sh/f7jeawyjgszwttu/AAAHnguxoB1XORHsB5J5_tKHa?dl=0

Crash ID: 635c0b4de2060f48928b3f2f254160d072d28d58

Stack Trace

SpatialIndex::MVRTree::Data::storeToByteArray :
qsort :
SpatialIndex::MVRTree::Data::storeToByteArray :
SpatialIndex::MVRTree::Data::storeToByteArray :
SpatialIndex::MVRTree::Data::storeToByteArray :
SpatialIndex::RTree::Data::getShape :
SpatialIndex::RTree::Data::getShape :
QgsSpatialIndex::addFeature :
QgsSpatialIndex::addFeature :
QgsInternalGeometrySnapper::snapFeature :
PyInit__analysis :
PyMethodDef_RawFastCallKeywords :
PyMethodDef_RawFastCallKeywords :
PyEval_EvalFrameDefault :
PyFunction_FastCallDict :
PyMethodDef_RawFastCallDict :
PyObject_Call :
PyInit_sip :
CPLStringList::empty :
PyInit__core :
QgsProcessingAlgorithm::runPrepared :
QgsProcessingAlgRunnerTask::run :
PyInit__core :
QgsTask::start :
QThreadPoolPrivate::reset :
QThread::start :
BaseThreadInitThunk :
RtlUserThreadStart :

QGIS Version: 3.4.3-Madeira
QGIS code revision: 2f64a3c4e7
Compiled against Qt: 5.11.2
Running against Qt: 5.11.2
Compiled against GDAL: 2.4.0
Running against GDAL: 2.4.0

System Info
CPU Type: x86_64
Kernel Type: winnt
Kernel Version: 10.0.17134

Test project.qgz (9.74 KB) Andy Whyte, 2019-01-07 02:41 PM


#1 Updated by Giovanni Manghi almost 4 years ago

  • Priority changed from Normal to High
  • Category changed from Unknown to Processing/QGIS

#2 Updated by Julien Cabieces almost 4 years ago

The issue comes from libspatialindex and has already been reported : https://github.com/libspatialindex/libspatialindex/issues/107

#3 Updated by Jürgen Fischer almost 4 years ago

  • Resolution set to up/downstream

#4 Updated by Giovanni Manghi almost 4 years ago

  • Status changed from Open to Closed

Also available in: Atom PDF