qgis / QGIS

QGIS is a free, open source, cross platform (lin/win/mac) geographical information system (GIS)
https://qgis.org
GNU General Public License v2.0
10.09k stars 2.93k forks source link

QGIS crashes with aggregate virtual column and linked tables #55338

Open immoblecher opened 8 months ago

immoblecher commented 8 months ago

What is the bug or the crash?

User Feedback

I have a parent table with a virtual column that calculates the number of "kandidates" that belong to the same id, which is one of the columns: _count( "kandidat_id" , group_by:= "skid")

Then I have a join with another table in a one-to-one relationship, which allows editing of the child table values. It seems, that when the child table has values in some or all of the columns I can edit values in the parent table and can accept these e.g. in the Identify form with . But if I have no values in the child table, w.o.w. the record would be created as soon as I add a value in one of the fields (cascade on), QGIS crashes on . But this is not cast in stone and occurs randomly. If I remove the virtual column all works as expected. I use a drag-and-drop form to edit the data.

The layers are loaded over ArcGIS REST, but I have also tried with direct PostGIS layers...same result.

Report Details

Python Stack Trace

Windows fatal exception: access violation

Current thread 0x0000362c (most recent call first):
<no Python frame>

Stack Trace


QgsBasicNumericFormat::showThousandsSeparator :
QgsVectorLayer::getFeatures :
QgsVectorLayerJoinBuffer::joinedFeatureOf :
QgsVectorLayerJoinBuffer::changeAttributeValue :
QgsVectorLayerJoinBuffer::changeAttributeValues :
QgsVectorLayer::changeAttributeValues :
QgsAttributeForm::saveEdits :
QgsAttributeForm::saveWithDetails :
QgsAttributeDialog::accept :
QObject::qt_static_metacall :
QDialogButtonBox::qt_static_metacall :
QObject::qt_static_metacall :
QAbstractButton::clicked :
QAbstractButton::click :
QAbstractButton::mouseReleaseEvent :
QWidget::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QApplicationPrivate::sendMouseEvent :
QSizePolicy::QSizePolicy :
QSizePolicy::QSizePolicy :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QGuiApplicationPrivate::processMouseEvent :
QWindowSystemInterface::sendWindowSystemEvents :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
main :
BaseThreadInitThunk :
RtlUserThreadStart :

QGIS Info QGIS Version: 3.28.10-Firenze QGIS code revision: e2edb9c468 Compiled against Qt: 5.15.3 Running against Qt: 5.15.3 Compiled against GDAL: 3.7.1 Running against GDAL: 3.7.1

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

Steps to reproduce the issue

grafik

Versions

QGIS-Version 3.28.10-Firenze QGIS-Codeversion e2edb9c468
Qt-Version 5.15.3
Python-Version 3.9.5
GDAL-Version 3.7.1
PROJ-Version 9.2.1
EPSG-Registraturdatenbankversion v10.088 (2023-05-13)
GEOS-Version 3.12.0-CAPI-1.18.0
SQLite-Version 3.41.1
PDAL-Version 2.5.5
PostgreSQL-Client-Version unknown
SpatiaLite-Version 5.1.0
QWT-Version 6.1.6
QScintilla2-Version 2.13.1
BS-Version Windows 10 Version 2009
       

Aktive Python-Erweiterungen AppendFeaturesToLayer | 1.5.0 nominatim | 1.4.5 quick_map_services | 0.19.33 SpreadsheetLayers | 2.1.0 db_manager | 0.1.20 processing | 2.12.99

QGIS-Version 3.28.10-Firenze QGIS-Codeversion e2edb9c468 Qt-Version 5.15.3 Python-Version 3.9.5 GDAL-Version 3.7.1 PROJ-Version 9.2.1 EPSG-Registraturdatenbankversion v10.088 (2023-05-13) GEOS-Version 3.12.0-CAPI-1.18.0 SQLite-Version 3.41.1 PDAL-Version 2.5.5 PostgreSQL-Client-Version unknown SpatiaLite-Version 5.1.0 QWT-Version 6.1.6 QScintilla2-Version 2.13.1 BS-Version Windows 10 Version 2009

Aktive Python-Erweiterungen AppendFeaturesToLayer 1.5.0 nominatim 1.4.5 quick_map_services 0.19.33 SpreadsheetLayers 2.1.0 db_manager 0.1.20 processing 2.12.99

Supported QGIS version

New profile

Additional context

Also tried on 3.32 Lima...same problem

agiudiceandrea commented 7 months ago

@immoblecher, thanks for reporting. Could you please actually try if the issue does occur also using a new QGIS user profile without any external plugin installed?

github-actions[bot] commented 7 months ago

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue. In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue. If there is no further activity on this issue, it will be closed in a week.

github-actions[bot] commented 6 months ago

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue. Or, if you have any further questions, there are also further support channels that can help you.

agiudiceandrea commented 6 months ago

@immoblecher, could you please actually try if the issue does occur also using a new QGIS user profile without any external plugin installed?

github-actions[bot] commented 5 months ago

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue. In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue. If there is no further activity on this issue, it will be closed in a week.