[Mesh] Crash when playing with level of details

[DelazJ]

What is the bug or the crash?

I was trying to understand how the mesh "Reduction factor" setting affects the number of 3D "levels of detail". So going back and forth between these two options in the layer prioperties dialog and at some point I got

Crash ID: 9114d34e7ebbb5d7d412f55f95d568a3045fb9dd

Stack Trace

QList::size :
QList::count qlist.h:359
QgsMeshDatasetGroupTreeItem::enabledDatasetGroupIndexes qgsmeshdataset.cpp:598
QgsMeshDatasetGroupListModel::rowCount qgsmeshdatasetgrouptreeview.cpp:512
QgsMeshDatasetGroupListModel::data qgsmeshdatasetgrouptreeview.cpp:522
QComboBox::itemText :
QComboBox::initStyleOption :
QComboBox::paintEvent :
QWidget::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify qgsapplication.cpp:509
QCoreApplication::notifyInternal2 :
QWidgetPrivate::drawWidget :
QWidgetPrivate::paintSiblingsRecursive :
QWidgetPrivate::paintSiblingsRecursive :
QWidgetPrivate::drawWidget :
QWidgetPrivate::paintSiblingsRecursive :
QWidgetPrivate::paintSiblingsRecursive :
QWidgetPrivate::paintSiblingsRecursive :
QWidgetPrivate::drawWidget :
QWidgetPrivate::paintSiblingsRecursive :
QWidgetPrivate::drawWidget :
QWidgetPrivate::moveRect :
QWidget::event :
QgisApp::event qgisapp.cpp:2120
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify qgsapplication.cpp:509
QCoreApplication::notifyInternal2 :
QCoreApplicationPrivate::sendPostedEvents :
qt_plugin_query_metadata :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
main main.cpp:1644
WinMain mainwin.cpp:197
__scrt_common_main_seh exe_common.inl:288
BaseThreadInitThunk :
RtlUserThreadStart :

QGIS Info
QGIS Version: 3.21.0-Master
QGIS code revision: b9e4db1c90
Compiled against Qt: 5.15.2
Running against Qt: 5.15.2
Compiled against GDAL: 3.3.1
Running against GDAL: 3.3.1

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

Steps to reproduce the issue

I was (heavily) playing with the options in Rendering and 3D tabs The dataset I was using is https://github.com/lutraconsulting/MDAL/blob/master/tests/data/grib/Madagascar.wave.7days.grb

Versions

QGIS Version: 3.21.0-Master QGIS code revision: b9e4db1c90 Compiled against Qt: 5.15.2 Running against Qt: 5.15.2 Compiled against GDAL: 3.3.1 Running against GDAL: 3.3.1

Supported QGIS version

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

New profile

• [ ] I tried with a new QGIS profile

Additional context

No response

[PeterPetrik]

@DelazJ any chance of screencast?

[vcloarec]

I can't reproduce when I play with "levels of details" but I have also a crash when I heavily undo/redo during mesh editing with 3D view and with the edited mesh as terrain. It could be the same issue... The crash happens with a built with Qt 5.12.8 (ubuntu 20.04) and as I don't have debug symbol for this version, I only know the crash could happen in a Qt3DNode. When I try to reproduce with a built with Qt 5.15.2 and debug symbol, I don't have any crash...

[alexbruy]

Is this still an Issue? I can't reproduce crash on latest master (beb28f6ffd) on Linux.

[github-actions[bot]]

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]]

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.