Qgis crashed from plugin Vector/Check geom

[scribaoliv]

What is the bug or the crash?

I just launched the built-in plugin from menu : Vector/Check Geometry to check a Lines layer.
After a few minutes, Qgis froze then ended prematurely.
This happens each time.

Message from the crash-reporter :
Python Stack Trace
Windows fatal exception: access violation
Thread 0x000046e0 (most recent call first):
File "C:\Users/Olivier/AppData/Roaming/QGIS/QGIS3\profiles\default/python\expressions\default.py"Windows fatal exception: access violation

Stack Trace
PyUnstable_InterpreterFrame_GetLine :
Py_DumpTracebackThreads :
Py_DumpTracebackThreads :
Py_DumpTracebackThreads :
Py_AtExit :
Py_AtExit :
RtlpCallVectoredHandlers :
RtlDispatchException :
KiUserExceptionDispatch :
QgsProcessingUtils::indicesToFields :
QgsAbstractFeatureSource::iteratorOpened :
QgsVectorLayerFeatureIterator::QgsVectorLayerFeatureIterator :
QgsVectorLayerFeatureSource::getFeatures :
QgsFeaturePool::getFeature :
QgsGeometryCheckerUtils::lineIntersections :
QgsGeometryCheckerUtils::LayerFeature::operator!= :
QgsGeometryDuplicateCheck::collectErrors :
QgsGeometryChecker::runCheck :
QgsGeometryChecker::runCheck :
QgsGeometrySnapper::qt_static_metacall :
QgsGeometrySnapper::featureSnapped :
QtConcurrent::ThreadEngineBase::run :
QThreadPoolPrivate::reset :
QThread::start :
BaseThreadInitThunk :
RtlUserThreadStart :

QGIS Info
QGIS Version: 3.42.0-M�nster
QGIS code revision: feb8023
Compiled against Qt: 5.15.13
Running against Qt: 5.15.13
Compiled against GDAL: 3.10.2
Running against GDAL: 3.10.2

System Info
CPU Type: x86_64
Kernel Type: winnt
Kernel Version: 10.0.22631
Win 11 (23H2)
File infos / source : auvergne-latest.osm.pbf (2024-12, from geofabrik) --> imported into a PostGIS database (v. 17) with osm2pgsql (v. 2.0, flex mode, generic.lua), no customization.

Steps to reproduce the issue

1. Open my project-file
2. Launch built-in plugin from Vector/Check geometry

Versions

<style type="text/css"> p, li { white-space: pre-wrap; } </style>

Version de QGIS	3.42.0-Münster
Révision du code	feb8023
Bibliothèques
Version de Qt	5.15.13
Version de Python	3.12.9
GDAL version	3.10.2
Version de Proj	9.5.1
Version de la base de données du registre EPSG	v11.022 (2024-11-05)
Version de GEOS	3.13.0-CAPI-1.19.0
Version de SQLite	3.46.1
Version de PDAL	2.8.3
Version du client PostgreSQL	17.3
Version de SpatiaLite	5.1.0
Version de QWT	6.3.0
Version de QScintilla2	2.14.1
Version de l'OS	Windows 11 Version 2009
Extensions Python actives
ArcheoCAD	3.2.2
cartography_tools	1.2.1
DsgTools	4.16.0
kmltools	3.2.2
latlontools	3.7.3
MemoryLayerSaver	5.0.2
multiple_layers_tools	1.2
networks	2.8.0
orfeoToolbox_provider	3.0.3
postgis_toolbox	1.2
qgis-maptiler-plugin	3.4.1
qgis2web	3.25.1
QuickOSM	2.3.2
quick_map_services	0.20.0
shapetools	3.5.1
db_manager	0.1.20
grassprovider	2.12.99
MetaSearch	0.3.6
processing	2.12.99

Version de QGIS 3.42.0-Münster Révision du code [feb8023](https://github.com/qgis/QGIS/commit/feb8023300)

Bibliothèques
Version de Qt
5.15.13
Version de Python
3.12.9
GDAL version
3.10.2
Version de Proj
9.5.1
Version de la base de données du registre EPSG
v11.022 (2024-11-05)
Version de GEOS
3.13.0-CAPI-1.19.0
Version de SQLite
3.46.1
Version de PDAL
2.8.3
Version du client PostgreSQL
17.3
Version de SpatiaLite
5.1.0
Version de QWT
6.3.0
Version de QScintilla2
2.14.1
Version de l'OS
Windows 11 Version 2009

Extensions Python actives
ArcheoCAD
3.2.2
cartography_tools
1.2.1
DsgTools
4.16.0
kmltools
3.2.2
latlontools
3.7.3
MemoryLayerSaver
5.0.2
multiple_layers_tools
1.2
networks
2.8.0
orfeoToolbox_provider
3.0.3
postgis_toolbox
1.2
qgis-maptiler-plugin
3.4.1
qgis2web
3.25.1
QuickOSM
2.3.2
quick_map_services
0.20.0
shapetools
3.5.1
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

No response

[agiudiceandrea]

Please try if the issue does occur also using a new QGIS user profile without any external third-party plugin installed. If it does, please provide the QGIS project file.

[scribaoliv]

Hello !Thank you for such a quick response! I followed your instructions: after creating a new, clean profile (without 3d-party plugins), I tested <Check geometries> on my project, and unfortunately, I get the same crash. Message from the crash-reporter : Python Stack Trace Windows fatal exception: access violation Thread 0x000041b4 (most recent call first):Stack TraceQgsProcessingUtils::indicesToFields :QgsAbstractFeatureSource::iteratorOpened :QgsDatabaseQueryLogEntry::QgsDatabaseQueryLogEntry :QgsDatabaseQueryLog::enabled :QgsVectorLayerFeatureIterator::nextFeatureFid :QgsVectorLayerFeatureIterator::fetchFeature :QgsAbstractFeatureIterator::nextFeature :QgsFeaturePool::getFeature :QgsGeometryCheckerUtils::lineIntersections :QgsGeometryCheckerUtils::LayerFeature::operator!= :QgsGeometryDuplicateNodesCheck::collectErrors :QgsGeometryChecker::runCheck :QgsGeometryChecker::runCheck :QgsGeometrySnapper::qt_static_metacall :QgsGeometrySnapper::featureSnapped :QtConcurrent::ThreadEngineBase::run :QThreadPoolPrivate::reset :QThread::start :BaseThreadInitThunk :RtlUserThreadStart : QGIS Info QGIS Version: 3.42.0-M�nster QGIS code revision: feb8023 Compiled against Qt: 5.15.13 Running against Qt: 5.15.13 Compiled against GDAL: 3.10.2 Running against GDAL: 3.10.2 System Info CPU Type: x86_64 Kernel Type: winnt Kernel Version: 10.0.22631 I am attaching the project I am working on. Thank you very much. ---------------------------------------------------- Le mercredi 19 mars 2025 à 19:53:21 UTC+1, Andrea Giudiceandrea ***@***.***> a écrit : Please try if the issue does occur also using a new QGIS user profile without any external third-party plugin installed. If it does, please provide the QGIS project file. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***> agiudiceandrea left a comment (qgis/QGIS#61087) Please try if the issue does occur also using a new QGIS user profile without any external third-party plugin installed. If it does, please provide the QGIS project file. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***> | | Sans virus.www.avast.com |

[agiudiceandrea]

@scribaoliv, it's not possible to provide a file via e-mail message. Please use the GitHub web interface in order to attach the QGIS project file (zipped) in a comment. Please also provide step-by-step instructions and the layer file (zipped) used with the Geometry Checker core plugin and all the relevant parameters set.

[scribaoliv]

Attached : my project + layers (subset of points / lines)

scribaoliv-project.zip

• param files.
  My step-by-step operations =

1. Download <https://download.geofabrik.de/europe/france/auvergne-latest.osm.pbf > (2024-12-11)
2. Run osm2pgsql (2.0) with flex output (style provided : generic.lua)
   cd /d "/osm2pgsql2-bin"
   osm2pgsql.exe -c -O flex -S ./flex-config/generic.lua -H localhost -P 5432 -d -U Olivier -W "/auvergne-latest.osm.pbf"
3. Create QGis project , load all geometry layers - EPSG = 4326
4. (I worked on symbology for quite a long time but... ) No change in data (fields, attributes, geom...)
5. Now I would like to orient some point-symbols ('crossing') so that they are perpendicular to the ways to which they belong.
   I first tried an expression for the rotation property = degrees(azimuth($geometry, closest_point(geometry(get_feature_by_id('lines', overlay_nearest('lines',way_id,map_get("tags",'highway') like '%%',1,0.0002)[0])), $geometry)))
   but this expression doesn't work at all (returns Null/0 for all elements) ...
6. I decide to isolate these elements from the layer (filter = map_get("tags",'highway')='crossing') --> new points-layer (geopackage) and create a few calculated fields to understand what's wrong.
7. New calc-field filled from this expression : overlay_nearest('lines',way_id,map_get("tags",'highway') like '%%',1,0.0002)[0] -- this perfectly works
8. New calc-fields and from : x(closest_point(geometry(get_feature_by_id('lines', NearestId)), $geometry)) -- this returns Null for all elements... After various tests I realized that the function <get_feature_by_id> doesn't work ; for example geom_to_wkt(geometry(get_feature_by_id('lines', NearestId))) returns Null for all elements.
9. I don't understand why, that's why I wanted to check the geometry of elements from layer.

Thanks

[scribaoliv]

EDIT : (I see that the web interface deleted some words...) In step 7. I create the field 'NearestId', and in step 8 'NearestX' and 'NearestY'
Only a small subset of points / lines is provided in attached zip

[agiudiceandrea]

The provided steps and project are not useful.

In order to replicate the issue:

• in a new project, import the "lines" layer from lines.gpkg in lines.zip
• open the Geometry Checker core plugin's dialog window, set the options "Line" and "Self intersections", run the checks
• see the crash

The issue doesn't occur running QGIS 3.40.4 while it occurs running QGIS 3.42.0 and QGIS 3.43.0-Master.